Showing content from http://mail.python.org/pipermail/python-dev/attachments/20090309/f9cceccf/attachment-0001.htm below:
<br><br><div class="gmail_quote">On Mon, Mar 9, 2009 at 20:25, Tennessee Leeuwenburg <span dir="ltr"><<a href="mailto:tleeuwenburg@gmail.com">tleeuwenburg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br><br>I am beginning reviewing some more issues in the tracker. I think it would be useful to have the following status options (new status options marked with a '+'):<br>Â Open: Means that the issue has been created and not further reviewed<br>
 + Request Approved: Means that the issue is marked as worth further development by the community<br> + Specification Approved: Means that the functionality to be developed is written down in some form, and agreed at least in general terms (preferably in fairly specific terms)<br>
 + Under Development: Means that an implementation is currently under development<br> Pending Feedback: Means that work is suspended pending feedback<br> + Under Final Review: Means that a patch has been submitted and may be a flag that core developers can usefully review the work done without having to revisit the whole process<br>
 Closed: Means that the issue is either suspended indefinitely or has been resolved (see resolution value)</blockquote><div><br> I assume you want all of this for the Status field, correct?<br><br>As for the options, some of these overlap with the Stage field. For instance, if something has been set to any stage other than "accepted/rejected" it means it needs to be looked into, so that duplicates your "Request Approved" status. Similar thing with the review stages and "Under Final Review".<br>
<br>But a general "under development" status would probably be worth adding. That way if an issue is "open" it needs attention, "Under development" means someone is working on a solution, "pending" means someone is blocking the issue for more information, and "closed" means closed.<br>
<br>One thing to watch out for, Tennessee, is getting too specific. Like your "Request Approved" and "Specification Approved" just seems too heavy-handed to my tastes. Personally, I prefer to make sure the issue workflow to be somewhat simple so that people don't end up arguing over stuff like whether something has been specified well enough to have it set to "Spec Approved" even if someone else disagrees (which you know would happen).<br>
<br>-Brett<br></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4