Re: [Scons-dev] Is Tigris issue tracking actively used?
Hi there, 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. after another bug scraping (thanks to everybody who volunteered!), I created two new HTML lists of the current state in our bugtracker. Please find those files attached for your convenience and general overview... Best regards, Dirk issues_overview.tgz Description: application/compressed-tar ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] Is Tigris issue tracking actively used?
On Mon, Jul 7, 2014 at 11:17 PM, Dirk Bächle tshor...@gmx.de wrote: On 07.07.2014 22:01, anatoly techtonik wrote: On Sun, Jul 6, 2014 at 3:25 PM, Andrew Featherstone andrew.featherst...@cantab.net 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? No. Sorry. Dirk made script to export tigris.org issues, which I saved here: https://bitbucket.org/techtonik/dataliberation/src/tip/issues/?at=default but Google deprecated their Issue API, probably due a lot of spam: https://code.google.com/p/support/wiki/IssueTrackerAPIPython Bitbucket supports import/export, but was considered awful by me: https://confluence.atlassian.com/display/BITBUCKET/Export+or+import+issue+data and then I stuck with reversing Roundup tracker model. Moving to Roundup as bug tracker got discussed recently on the dev ML: http://two.pairlist.net/pipermail/scons-dev/2014-May/001369.html I have patched the export scripts from the dataliberation repo above, and am able to export most of the current Tigris tracker's info to a Roundup instance. I also have two final pull requests pending at OpenHatch: https://github.com/openhatch/oh-bugimporters/pull/57 https://github.com/openhatch/oh-mainline/pull/293 which will make our database available (read-only) via their Roundup tracker. Nice. I added incremental download to dataliberation project and will to see how to convert stuff with OpenRefine. -- anatoly t. ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] Is Tigris issue tracking actively used?
I'm likewise, William, but I think that all users can add some value by wandering through the open issue list and seeing if we can improve things by clearing issues that are known to be resolved, testing old issues against current versions of SCons, etc. Dirk, I've started traipsing through the open bugs, looking for things I think already are fixed, or verifying if issues are still present, and commenting accordingly. At 4 issues a day it'd be 3 months before the open issues list has boiled down to nothing, but hopefully just keeping a downward trend on this for a period will feel worthwhile. The roadmap is a high-level thing, and doesn't explain for example what triggered the 2.3.2 release, which I'm interested in understanding. Cheers, Andrew P.S. on the homepage the links to the individual mailing lists point to the old Tigris ones. Can they point at the Mailman-based ones instead? On Mon, 07 Jul 2014 02:48:39 +0100, William Blevins wblevins...@gmail.com wrote: I'm a bit green around the SCons code base, but I agree with Andrew that the Tigris bug tracking looks *scary* at a glance. I would be willing to help if I know enough to be helpful. As a side note, I started to some discussions about Java toolchain issues and I will get back on those; got side-tracked with the performance conversations, but some profiles came out of it which I thought were helpful. V/R, William On Sun, Jul 6, 2014 at 5:19 PM, Dirk Bächle tshor...@gmx.de mailto:tshor...@gmx.de wrote: Andrew, On 06.07.2014 22:25, Andrew Featherstone wrote: Hi Dirk, Ok it's good to know where to be looking. For me the number of open issues gives a (false) negative impression that the project's development is stale. For me, P1 bugs are triaged as is an issue which causes detrimental behaviour (e.g. deletes source code, compiles source code with different flags, misses changes in source code), and must be fixed in the next release. Only two of the P1 issues have been commented on in the past two years, and some have sat still since 2009! As I said, this is confusing at best to someone who wants to get a feel for the current status of an open source project. I can only agree. ;) That's why I started to do something about it...would you like to help? Moving forwards it'd be nice to know that tackling issues in the issue tracker is worthwhile, that comments don't go unread, etc. Who marks what issues must be fixed for the next version? Is there any plan for existing issues to be updated? Do the developers communicate through the issue tracker or some other method e.g. IRC? Regarding issues there is no real planning or update process in place. We used to have a triaging process (BugParty) via IRC, on a bi-weekly basis...but with the dwindling number of core developers it petered out. At the moment, the development version is quite stable. I don't know of any showstopper bugs that would have to get fixed immediately (no P1 issues). The few really serious issues get discussed and assigned here on the dev ML. We also have a small roadmap at http://scons.org/wiki/Roadmap ...aaand that's it, I guess. Regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org mailto:Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] Is Tigris issue tracking actively used?
Andrew, On 07.07.2014 19:47, Andrew Featherstone wrote: I'm likewise, William, but I think that all users can add some value by wandering through the open issue list and seeing if we can improve things by clearing issues that are known to be resolved, testing old issues against current versions of SCons, etc. Dirk, I've started traipsing through the open bugs, looking for things I think already are fixed, or verifying if issues are still present, and commenting accordingly. At 4 issues a day it'd be 3 months before the open issues list has boiled down to nothing, but hopefully just keeping a downward trend on this for a period will feel worthwhile. thanks so much for all the work you've done so far! The roadmap is a high-level thing, and doesn't explain for example what triggered the 2.3.2 release, which I'm interested in understanding. Cheers, Andrew P.S. on the homepage the links to the individual mailing lists point to the old Tigris ones. Can they point at the Mailman-based ones instead? That's #2947 already. ;) Dirk ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] Is Tigris issue tracking actively used?
On 07.07.2014 22:01, anatoly techtonik wrote: On Sun, Jul 6, 2014 at 3:25 PM, Andrew Featherstone andrew.featherst...@cantab.net 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? No. Sorry. Dirk made script to export tigris.org issues, which I saved here: https://bitbucket.org/techtonik/dataliberation/src/tip/issues/?at=default but Google deprecated their Issue API, probably due a lot of spam: https://code.google.com/p/support/wiki/IssueTrackerAPIPython Bitbucket supports import/export, but was considered awful by me: https://confluence.atlassian.com/display/BITBUCKET/Export+or+import+issue+data and then I stuck with reversing Roundup tracker model. Moving to Roundup as bug tracker got discussed recently on the dev ML: http://two.pairlist.net/pipermail/scons-dev/2014-May/001369.html I have patched the export scripts from the dataliberation repo above, and am able to export most of the current Tigris tracker's info to a Roundup instance. I also have two final pull requests pending at OpenHatch: https://github.com/openhatch/oh-bugimporters/pull/57 https://github.com/openhatch/oh-mainline/pull/293 which will make our database available (read-only) via their Roundup tracker. Regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] Is Tigris issue tracking actively used?
On 07/07/14 21:17, Dirk Bächle wrote: On 07.07.2014 22:01, anatoly techtonik wrote: On Sun, Jul 6, 2014 at 3:25 PM, Andrew Featherstone andrew.featherst...@cantab.net 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? No. Sorry. Dirk made script to export tigris.org issues, which I saved here: https://bitbucket.org/techtonik/dataliberation/src/tip/issues/?at=default but Google deprecated their Issue API, probably due a lot of spam: https://code.google.com/p/support/wiki/IssueTrackerAPIPython Bitbucket supports import/export, but was considered awful by me: https://confluence.atlassian.com/display/BITBUCKET/Export+or+import+issue+data and then I stuck with reversing Roundup tracker model. Moving to Roundup as bug tracker got discussed recently on the dev ML: http://two.pairlist.net/pipermail/scons-dev/2014-May/001369.html I have patched the export scripts from the dataliberation repo above, and am able to export most of the current Tigris tracker's info to a Roundup instance. I also have two final pull requests pending at OpenHatch: https://github.com/openhatch/oh-bugimporters/pull/57 https://github.com/openhatch/oh-mainline/pull/293 which will make our database available (read-only) via their Roundup tracker. Regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev Whilst the project may not like Github or Bitbucket's in built issue trackers, personally rolling your own comes across as a really good way to minimise the number of people who contribute to the SCons project. Each unfamiliar technology, new account to set up, etc forms a hurdle, and eventually people just stop jumping. I've only every heard of Roundup on this list, and Tigris is dying but at least it exists and can and is being used today. It's the dev team's prerogative to move from tracker to tracker, but please let's not sidetrack a thread on how can I make the project better today with conjecture and what-ifs. Cheers, Andrew ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] Is Tigris issue tracking actively used?
Hi Dirk, Ok it's good to know where to be looking. For me the number of open issues gives a (false) negative impression that the project's development is stale. For me, P1 bugs are triaged as is an issue which causes detrimental behaviour (e.g. deletes source code, compiles source code with different flags, misses changes in source code), and must be fixed in the next release. Only two of the P1 issues have been commented on in the past two years, and some have sat still since 2009! As I said, this is confusing at best to someone who wants to get a feel for the current status of an open source project. Moving forwards it'd be nice to know that tackling issues in the issue tracker is worthwhile, that comments don't go unread, etc. Who marks what issues must be fixed for the next version? Is there any plan for existing issues to be updated? Do the developers communicate through the issue tracker or some other method e.g. IRC? Regards, Andrew ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
Re: [Scons-dev] Is Tigris issue tracking actively used?
Andrew, On 06.07.2014 22:25, Andrew Featherstone wrote: Hi Dirk, Ok it's good to know where to be looking. For me the number of open issues gives a (false) negative impression that the project's development is stale. For me, P1 bugs are triaged as is an issue which causes detrimental behaviour (e.g. deletes source code, compiles source code with different flags, misses changes in source code), and must be fixed in the next release. Only two of the P1 issues have been commented on in the past two years, and some have sat still since 2009! As I said, this is confusing at best to someone who wants to get a feel for the current status of an open source project. I can only agree. ;) That's why I started to do something about it...would you like to help? Moving forwards it'd be nice to know that tackling issues in the issue tracker is worthwhile, that comments don't go unread, etc. Who marks what issues must be fixed for the next version? Is there any plan for existing issues to be updated? Do the developers communicate through the issue tracker or some other method e.g. IRC? Regarding issues there is no real planning or update process in place. We used to have a triaging process (BugParty) via IRC, on a bi-weekly basis...but with the dwindling number of core developers it petered out. At the moment, the development version is quite stable. I don't know of any showstopper bugs that would have to get fixed immediately (no P1 issues). The few really serious issues get discussed and assigned here on the dev ML. We also have a small roadmap at http://scons.org/wiki/Roadmap ...aaand that's it, I guess. Regards, Dirk ___ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
