D tool development workflow

Russel Winder <[email protected]> Tue, 18 Apr 2017 09:07:32 +0100

Newsgroups	gmane.comp.programming.tools.scons.devel
Message-ID	<[email protected]>

I believe that development of the D tools is going to be improved by
assuming that other D tool users want to work with a standard SCons and
updates just to the D tools; that they are not interested in working
with SCons from a Mercurial clone that has to be managed. I am
therefore going to make https://github.com/russel/SCons_D_Experiment
the focus of all D tool evolution and then providing pull requests to
the SCons BitBucket mainline. A little more work for me in that I
develop in one repository and then update another, but the D world is a
Git world and so using a Git repository is more natural for handling
experiments.

I am also going to break ranks and have D tool issues come in to this
repository. D folk are GitHub folk, I am not going to push them to
Tigris for bug reporting – especially as I never go there myself any
more.

This is about pragmatics, I believe more will be achieved this way.

Hopefully, what has started is a race for SCons and Meson to beat Dub
in building D code.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[email protected]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [email protected]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev

signature.asc (application/pgp-signature, 833 B)