Hello. I'm considering changing issue tracker as apparently a lot of people gave feedback after the release. For me the current incarnation is unbearable - I can't easily track things like "submitted" or "triaged" from "windows build requires superuser" which always pop at the top or "polish objspace initialization" which is probably important but I already decided not to deal with it. It might be the inherent problem with roundup or just our implementation. pylib for example moved to bitbucket, probably also for similar reasons. Do you have any thoughts or obvious choices? Cheers, fijal
On Sun, Mar 14, 2010 at 1:04 AM, Maciej Fijalkowski <fijall@gmail.com> wrote:
Hello.
I'm considering changing issue tracker as apparently a lot of people gave feedback after the release. For me the current incarnation is unbearable - I can't easily track things like "submitted" or "triaged" from "windows build requires superuser" which always pop at the top or "polish objspace initialization" which is probably important but I already decided not to deal with it.
It might be the inherent problem with roundup or just our implementation. pylib for example moved to bitbucket, probably also for similar reasons.
Do you have any thoughts or obvious choices?
Cheers, fijal _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
I'd say trac is the "obvious" choice since we are on svn. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me
On 14 March 2010 20:04, Maciej Fijalkowski <fijall@gmail.com> wrote:
Hello.
I'm considering changing issue tracker as apparently a lot of people gave feedback after the release. For me the current incarnation is unbearable - I can't easily track things like "submitted" or "triaged" from "windows build requires superuser" which always pop at the top or "polish objspace initialization" which is probably important but I already decided not to deal with it.
It might be the inherent problem with roundup or just our implementation. pylib for example moved to bitbucket, probably also for similar reasons.
Do you have any thoughts or obvious choices?
There's always Launchpad; it's not perfect but if it works for ubuntu it must be at least OK :-) Also, someone else runs the server, which probably isn't to be discounted, and can probably be relied on to improve over time -- there's a lot of development happening on it. It does all the usual things reasonably well, with sensible statuses and tagging and assignment and so on. Possibly a disadvantage is that because it has a focus on collaboration between projects, it's not tweakable to meet any particular project's needs. It should be possible to import the bugs from roundup into lp, although roundup's 'build your own schema' thing probably means some hand-holding will be required. Cheers, mwh
2010/3/14 Maciej Fijalkowski <fijall@gmail.com>:
Hello.
I'm considering changing issue tracker as apparently a lot of people gave feedback after the release. For me the current incarnation is unbearable - I can't easily track things like "submitted" or "triaged" from "windows build requires superuser" which always pop at the top or "polish objspace initialization" which is probably important but I already decided not to deal with it.
It might be the inherent problem with roundup or just our implementation. pylib for example moved to bitbucket, probably also for similar reasons.
Do you have any thoughts or obvious choices?
Perhaps we can try and get a python.org roundup tracker. Jython does this, and the CPython one is quite bearable. -- Regards, Benjamin
participants (4)
-
Alex Gaynor -
Benjamin Peterson -
Maciej Fijalkowski -
Michael Hudson-Doyle