On Fri, Oct 23, 2009 at 1:49 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:
Brett Cannon wrote:
Another summit, another potential time to see if people want to change anything about the issue tracker. I would bring up:
- Dropping Stage in favor of some keywords (e.g. 'needs unit test', 'needs docs') - Adding a freestyle text box to delineate which, if any, stdlib module is the cause of a bug and tie that into Misc/maintainers.rst; would potentially scale back the Component box
+lots on adding a module field (independent of automatically adding maintainers to the nosy list, it would assist in "I just did a major cleanup of module X, are there any old bugs I can kill off").
yet another feature request or two to be lost to a mailing list thread along those lines: Maintainer or not i'd like to be able to setup triggers so that i'm automatically cc'ed on any bugs matching a simple search query i specify. The email sent out to people cc'ed when a new bug is opened and unassigned should have a simple links in it when cc'ed to someone who can be assigned bugs: 'Assign to me' that if followed will assign that bug to them without requiring a login.
Of course, it will take a while for the field to be filled in on existing issues, but even having it be possible would be very nice.
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/greg%40krypto.org