[Scons-dev] Is Tigris issue tracking actively used?

[Dirk Bächle]

Hi Andrew,

On 06.07.2014 14:25, Andrew Featherstone wrote:
> Hi All,
>
> I was wondering what the current state of issue tracking is for the 
> SCons project. There was some talk a little while back about moving 
> away from Tigris to a different issue tracker, has that happened? I 
> thought I'd have a quick look on Tigris, but clicking "All Open 
> Issues" returns a warning that there are too many issues to be 
> displayed! Viewing open bugs and sorting to priority gives a large 
> chunk of bugs that haven't be touched in years, and some of which look 
> like they are resolved (e.g. issue 1985 
> <http://scons.tigris.org/issues/show_bug.cgi?id=1985> looks like it's 
> implemented here 
> <http://www.scons.org/doc/2.3.1/HTML/scons-user.html#f-Platform>). 
> It's confusing that there are open P1 bugs that don't make it into 
> subsequent releases, or at least have a comment that explains why 
> they're being pushed to release n+1.
>
> What's the model used for triaging and resolving issues? The "we're 
> looking, so email us" approach on http://www.scons.org/dev.php feels a 
> bit old-fashioned, particularly compared to the "social coding" feel 
> you get on Github where you can comment on an issue, create a branch 
> on a fork and try to close the issue via a pull request.
>
the Tigris tracker is still active at the moment, migration to other 
options (GoogleCode/Roundup) has started. It's mainly used to collect 
bug reports from users that aren't able to provide patches/fixes on 
their own. So they get into the queue, waiting for a developer to pick 
them up. I recently initiated a bug scraping to reduce the number of 
open issues, see:

   http://two.pairlist.net/pipermail/scons-dev/2014-May/001369.html
   http://two.pairlist.net/pipermail/scons-dev/2014-May/001417.html
   http://two.pairlist.net/pipermail/scons-dev/2014-May/001424.html

If you find an issue that you can fix immediately, go ahead and create a 
pull request please ( see also 
http://scons.org/wiki/DeveloperGuide/Introduction ). After switching the 
VCS to Mercurial/Bitbucket this is the preferred method for getting 
changes into the core. The webpages, and the somewhat misleading fact 
that the Tigris tracker is still in place, may draw a different 
picture...if you have ideas for making things more clear to other users, 
let us know please.

Best regards,

Dirk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20140706/a68778a8/attachment.html>