Barry Warsaw barry at python.org
Fri Dec 5 14:12:44 CET 2008

• Previous message: [python-committers] release26-maint branch is thawed
• Next message: [python-committers] [Python-Dev] RELEASED Python 3.0 final
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=> python-committers

On Dec 5, 2008, at 3:21 AM, Georg Brandl wrote:

>> In the meantime, I'll make sure Georg is involved in point releases
>> moving forward.
>
> That's good. Thanks!

I think the way I'd like to handle this is through the python- 
committers mailing list.  I propose the following workflow:

* PEP 101 is followed up to making the release tag
* Send a message to p-c indicating the tag revision (probably a  
forward of the commit msg)
* Before a) pushing the new web content, b) sending the announcment,  
wait for the "Go" signal from the following experts: WE, DE (we can  
amend that list in the future).  The "Go" signal is also sent to p-c.

How does that sounds?  PEP 101 kinda sorta says this but if you're  
okay with this workflow, I'll make it explicit.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSTkozHEjvBPtnXfVAQKkgwQAr/uPXf9XHdToROo/PLt+rmCCCeWCOCDM
ecOshm8ttHV8KbGfRosPIiKFD7iP/NTsOEfaBI1FJrddsOO5LWptEAei2laY/pkI
gyNiNYVjIA0PQsejzdm3GQPqRqRLdLWrKswGq9xC5Tpd1r7Cwyqw1J0LgXY9mtsI
bzlKyP4Vzm0=
=hCC9
-----END PGP SIGNATURE-----

---

• Previous message: [python-committers] release26-maint branch is thawed
• Next message: [python-committers] [Python-Dev] RELEASED Python 3.0 final
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list