[Scons-dev] Roundup tracker demo instance...

William L Blevins wblevins001 at gmail.com
Mon Sep 28 08:56:33 EDT 2015



On September 28, 2015, at 1:43 PM, Russel Winder <russel at winder.org.uk> wrote:

>On Sun, 2015-09-27 at 15:03 -0700, Bill Deegan wrote:
>> Maybe worth sticking in a scons bitbucket repo?
>> 
>[…]
>A DVCS repository is indeed where all code belongs :-)
>In this case I think this is very important. Whatever the rights and
>wrongs of issue trackers other than Tigris, I feel it is important to
>have integration between the code repository, pull requests, and the
>issue tracker. The current situation is viable, but significantly less
>than mediocre, let alone optimal.
>If there is a JIRA instance we can bind to the Mercurial repository on
>BitBucket then we should go for it.  Even if in the far distant future
>Atalassian force a Mercurial → Git move on BitBucket, they will retain
>JIRA as the associated issue tracker.
>Having used JIRA at Codehaus for the Groovy stuff, I can attest that
>JIRA is not awful and indeed is far superior to Tigris.
>Thus, for me, shifting the issues from Tigris to a JIRA  directly
>associated with BitBucket is a Huge Win™. 
I have used Jira and I think if we can get free instances for the project, then the direct jira -> bitbucket <- confluence setup will give us a lot of project management control.
>-- 
>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 --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20150928/d301495f/attachment.html>


More information about the Scons-dev mailing list