On Fri, 2017-04-21 at 09:41 -0700, Bill Deegan wrote: > Russel, > > At present I'm spending all my available energy and time on getting > py2+py3 > working. > Once that is done, then we can look at migrating the bug tracker, but > not > before.
Exactly, getting the Python 3 stuff finished clearly takes higher priority than anything just now, it is the current sprint. I'll see if I can take a look at more this weekend. Next week is ACCU so I'll likely be unable to do anything constructive on any project. https://conference.accu.org/site/ > That said, I'm thinking post 3 a migration to github could have some > real > value. > (And git, I'm tired of using HG on only this project) I would find workflow very much easier using Git rather than Mercurial for this project. The issue for me is in-repository transient branches for short-lived feature branches. With my knowledge of Mercurial, whilst nice for individual use, is a pain for managing a mainline clone and multiple feature branches. I am happy using BitBucket, but would also be happy with GitHub, or even GitLab. > Also note that buildbot (our current ci http://buildbot.scons.org/ ) > is > capable of pushing ci status to bitbucket (and github as > well). Travis-CI > builds work for plain python builds, but very unlikely the > VM/Containers > the tests are run in will have many of the installed tools we use in > many > tests, and also most likely not have any MSVS versions installed.. I think this discussion should switch to an own thread. The advantage of Travis-CI if we can get away with it is having various OS installations. For the D tools, it is possible to create a build matrix for all eight variations of D compiler. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev