Message141568
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 :) |
|
Date |
User |
Action |
Args |
2011-08-02 15:07:12 | r.david.murray | set | recipients:
+ r.david.murray, docs@python |
2011-08-02 15:07:11 | r.david.murray | set | messageid: <1312297631.98.0.460065012433.issue12682@psf.upfronthosting.co.za> |
2011-08-02 15:07:11 | r.david.murray | link | issue12682 messages |
2011-08-02 15:07:10 | r.david.murray | create | |
|