I'm really ashamed. The SRE bug #1072259, reported in 2004-11-24, and fixed a few minutes ago, got into 2.4 final. The only reason it wasn't fixed on time for 2.4 is because I wasn't aware about it. :-( Is there any way to get notified about certain kinds of bugs in SourceForge? Or, is there any way to follow all new bugs posted? Or even, what's the easiest way to avoid that problem by being notified of bugs as soon as possible? Thank you, and I'm sorry. -- Gustavo Niemeyer http://niemeyer.net
On Thu, Dec 02, 2004 at 02:31:06PM -0200, Gustavo Niemeyer wrote:
in SourceForge? Or, is there any way to follow all new bugs posted? Or even, what's the easiest way to avoid that problem by being notified of bugs as soon as possible?
Kurt's weekly bug summaries list all new bugs. For a sample, see http://mail.python.org/pipermail/python-list/2004-December/252968.html ; they get posted to python-dev, too. Perhaps the summaries should include an "unassigned bugs" list to nag us to look at bugs and assign them to the right person. --amk
"A.M. Kuchling"
Perhaps the summaries should include an "unassigned bugs" list to nag us to look at bugs and assign them to the right person.
The bug report is derived from the bug and patch email lists, so that information isn't available without scraping it off SF. However, the SF trackers can be set to query for Unassigned / Open. It looks like about 2/3 of the open bugs and 3/4 of the open patches are unassigned. I often unassign IDLE bugs that I'm not planning to fix right now, hoping that may encourage someone to step forward by removing the illusion that something is happening. Conversely, if I make progress on an unassigned bug/patch, I'll assign it to myself as an indication that it's being worked on, avoiding duplication of effort. I track IDLE bugs via the IDLE category. That's very useful, maybe we need more categories? -- KBK
Is there any way to get notified about certain kinds of bugs in SourceForge? Or, is there any way to follow all new bugs posted? Or even, what's the easiest way to avoid that problem by being notified of bugs as soon as possible?
After some googling I've found python-bugs-list. Mentioning it in http://www.python.org/community/lists.html might be a good idea. Additional suggestions still accepted. Thanks! -- Gustavo Niemeyer http://niemeyer.net
FYI, I just changed SF so that bugs with Category "Regular Expressions" are auto-assigned to Gustavo (they were being auto-assigned to Fredrik, which doesn't appear to do much good anymore). [Gustavo Niemeyer]
I'm really ashamed. The SRE bug #1072259, reported in 2004-11-24, and fixed a few minutes ago, got into 2.4 final. The only reason it wasn't fixed on time for 2.4 is because I wasn't aware about it. :-(
Unfortunately, that particular bug was in a wrong Category, so the new auto-assign wouldn't have helped here anyway.
participants (4)
-
A.M. Kuchling
-
Gustavo Niemeyer
-
kbk@shore.net
-
Tim Peters