[docs] [issue12682] Meaning of 'accepted' resolution as documented in devguide
report at bugs.python.org
Wed Aug 3 03:15:09 CEST 2011
Senthil Kumaran <senthil at uthcode.com> added the comment:
I thought "fixed" was enough. A kind of binary state where we say, okay we have it and otherwise no, we don't. I know for feature requests the terminology does not make sense, but I believe I have worked with bug trackers where fixed was the ultimate state where a particular change (be a bug-fix or a feature request) was in the code.
Well, as long as it is helpful, I am fine with it, but too many options can confuse (just as 'accepted' did) and it will be helpful to prune down some.
resolution: accepted ->
Python tracker <report at bugs.python.org>
More information about the docs