Issue workflow doc is now live
I sent this out as a Google Doc a while back, but I just did a proof-reading, converted it, and pushed it live to the python.org: http://www.python.org/dev/workflow/ . So now people who ever triage issues have a guide to follow if they are not sure how to set things.
-Brett
P.S.: Doing this doc has made me realize that our issue workflow still feels off and SF-influenced. If people want to talk at PyCon about it just let me know. I might try to get a discussion going during the language summit or at the sprints as I have some ideas on how to simplify thing but make it usable for more people (preview: I like how http://code.djangoproject.com/querydoes their tickets).
Brett Cannon wrote:
I sent this out as a Google Doc a while back, but I just did a proof-reading, converted it, and pushed it live to the python.org http://python.org: http://www.python.org/dev/workflow/ . So now people who ever triage issues have a guide to follow if they are not sure how to set things.
Does that mean PEP 3 should be Withdrawn or does it mean it should be replaced?
Cheers, Nick.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 23, 2009, at 8:31 AM, Nick Coghlan wrote:
Brett Cannon wrote:
I sent this out as a Google Doc a while back, but I just did a proof-reading, converted it, and pushed it live to the python.org http://python.org: http://www.python.org/dev/workflow/ . So now people who ever triage issues have a guide to follow if they are not sure how to set things.
Does that mean PEP 3 should be Withdrawn or does it mean it should be replaced?
It should probably be replaced with Brett's document. Barry
On Mon, Mar 23, 2009 at 05:36, Barry Warsaw barry@python.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 23, 2009, at 8:31 AM, Nick Coghlan wrote:
Brett Cannon wrote:
I sent this out as a Google Doc a while back, but I just did a proof-reading, converted it, and pushed it live to the python.org http://python.org: http://www.python.org/dev/workflow/ . So now people who ever triage issues have a guide to follow if they are not sure how to set things.
Does that mean PEP 3 should be Withdrawn or does it mean it should be replaced?
It should probably be replaced with Brett's document.
I say replace as well.
-Brett
I sent this out as a Google Doc a while back, but I just did a proof-reading, converted it, and pushed it live to the python.org <http://python.org> <http://python.org>: http://www.python.org/dev/workflow/ . So now people who ever triage issues have a guide to follow if they are not sure how to set things. Does that mean PEP 3 should be Withdrawn or does it mean it should be replaced? It should probably be replaced with Brett's document.I say replace as well.
Will then dev/workflow be removed? I don't think we need two copies (possibly inconsistent)? So if dev/workflow stays, PEP 3 should be withdrawn.
Regards, Martin
On Mon, Mar 23, 2009 at 17:01, "Martin v. Löwis" martin@v.loewis.de wrote:
I sent this out as a Google Doc a while back, but I just dida
proof-reading, converted it, and pushed it live to the python.org <http://python.org> <http://python.org>: http://www.python.org/dev/workflow/ . So now people who ever triage issues have a guide to follow if they are not sure how to set things. Does that mean PEP 3 should be Withdrawn or does it mean it should be replaced? It should probably be replaced with Brett's document.I say replace as well.
Will then dev/workflow be removed? I don't think we need two copies (possibly inconsistent)? So if dev/workflow stays, PEP 3 should be withdrawn.
Sorry I wasn't clear; that's what I meant by replace; withdraw PEP 3 and have a note pointing to /dev/workflow, not turn /dev/workflow into a new version of PEP 3.
-Brett
participants (4)
-
"Martin v. Löwis" -
Barry Warsaw -
Brett Cannon -
Nick Coghlan