[docs] [issue12682] Meaning of 'accepted' resolution as documented in devguide

R. David Murray report at bugs.python.org
Tue Aug 2 17:07:12 CEST 2011

New submission from R. David Murray <rdmurray at bitdance.com>:

The devguide documents the 'accepted' resolution as follows:

     Submitted patch was applied, still needs verifying (for example by
     watching the buildbots) that everything went fine. At that point the
     resolution should be set to fixed and the status changed to closed.

I've never run into this usage while working with the tracker.  I *have* seen people set 'accepted' when they want to indicate that the issue is considered valid to be fixed, or that a feature request has been accepted but there's no patch ready for commit yet.

Formally I believe that the 'accepted' resolution is for committed feature requests (since "fixed" doesn't make English sense in that context).  Any other use is creative license :)

assignee: docs at python
components: Documentation
messages: 141568
nosy: docs at python, r.david.murray
priority: normal
severity: normal
status: open
title: Meaning of 'accepted' resolution as documented in devguide

Python tracker <report at bugs.python.org>

More information about the docs mailing list