[Python-Dev] Small RFEs and the Bug Tracker
Nick Coghlan
ncoghlan at gmail.com
Tue Feb 19 12:05:07 CET 2008
More information about the Python-Dev mailing list
Tue Feb 19 12:05:07 CET 2008
- Previous message: [Python-Dev] Small RFEs and the Bug Tracker
- Next message: [Python-Dev] Small RFEs and the Bug Tracker
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Christian Heimes wrote: > Steve Holden wrote: >> There there's the Status field. I understand "open" and "closed", but >> what's the semantic of "pending". Is it awaiting triage, awaiting status >> assignment, or what? > > I've used pending for two states. For one I've put an issue on pending > state when it was fixed on the trunk but we haven't decided if the bugs > needs to be fixed in 2.5 as well. I've also set old bugs as pending to > give the op a change to reopen the bug within a month. I've used pending for the former case as well (i.e. when I wanted a verdict from the release manager on whether or not to backport a particular fix to 2.5, but didn't want the issue hanging around as open when I had already fixed it for the trunk). We really do need to write some of this down in an information track PEP so we're all using the same values to mean the same thing... Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia --------------------------------------------------------------- http://www.boredomandlaziness.org
- Previous message: [Python-Dev] Small RFEs and the Bug Tracker
- Next message: [Python-Dev] Small RFEs and the Bug Tracker
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list