[Python-Dev] Proposed revision of PEP 3 (using the issue tracker)
Nick Coghlan
ncoghlan at gmail.com
Sat Feb 23 06:40:54 CET 2008
More information about the Python-Dev mailing list
Sat Feb 23 06:40:54 CET 2008
- Previous message: [Python-Dev] Please sign up for the PyCon sprint if you are attending!
- Next message: [Python-Dev] Proposed revision of PEP 3 (using the issue tracker)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I've attached a proposed revision of PEP 3 below. Feedback would be appreciated, and once we have a reasonable consensus that it accurately describes our current processes I can check it in and Martin can update the tracker to reflect any changes. It is intentional that the current non-resolution resolutions like 'later' are missing - I think those should definitely be retired. I also left out the 'compile error' type - I would prefer to see the Compiler added to the Components list so we can attach feature requests to it as well as bugs. One question I did have is whether or not access to 'security' type issues is automatically limited to a small subset of the developers. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia --------------------------------------------------------------- http://www.boredomandlaziness.org -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: pep-0003.txt Url: http://mail.python.org/pipermail/python-dev/attachments/20080223/02d73e30/attachment-0001.txt
- Previous message: [Python-Dev] Please sign up for the PyCon sprint if you are attending!
- Next message: [Python-Dev] Proposed revision of PEP 3 (using the issue tracker)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list