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

[Andrew Featherstone]

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.

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