[Python-Dev] Small RFEs and the Bug Tracker
Georg Brandl
g.brandl at gmx.net
Mon Feb 18 22:39:04 CET 2008
More information about the Python-Dev mailing list
Mon Feb 18 22:39:04 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 ]
Steve Holden schrieb: > Jeroen Ruigrok van der Werven wrote: >> -On [20080218 21:41], Brett Cannon (brett at python.org) wrote: >>> My issue with keeping the RFEs in the tracker as they are is that it >>> artificially inflates the open issue count. Python does not have over >>> 1,700 open bugs. >> >> An issue does not necessarily mean the same as bug. :) >> >> Is it a bug tracker you have or an issue tracker? If the former, agreed, if >> the latter then it makes sense to track RFEs in the tracker. >> > Certainly, but since some issues *are* bugs we might need to refine our > analysis somewhat. It would be better to have a bug report which omitted > issues of type "rfe". As far as I can see open issues of all other types > would be properly classified as bugs. > > 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? It's a leftover from SF.net. There it had the feature that pending items were closed automatically after two weeks if no further activity took place. For the new tracker, we should really decide about a "pending" policy, or implement the feature too. Georg
- 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