Barry Warsaw barry at python.org
Tue May 12 21:03:26 CEST 2015

• Previous message (by thread): [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
• Next message (by thread): [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On May 12, 2015, at 10:38 AM, Larry Hastings wrote:

>It doesn't.  Workflows 0 and 2 mean no public development of 3.6 until after
>3.5.0 final ships, as per tradition.

I still think it's a good idea to focus primarily on 3.5 while it's in the
beta/rc period, but if you want to allow for landings on what will be 3.6,
then going with workflow 1 will be an interesting social experiment.

I'm fine with any of them as long as the workflow is *well documented*,
preferably in the devguide.

Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/python-committers/attachments/20150512/4f5e2aad/attachment.sig>

---

• Previous message (by thread): [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
• Next message (by thread): [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list