[Scons-dev] D tool development workflow

[Russel Winder]

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:russel.winder at ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel at winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20170418/b5d02466/attachment.pgp>