-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Oct 7, 2008, at 5:47 PM, Nick Coghlan wrote: > Barry Warsaw wrote: >> On Oct 6, 2008, at 9:48 PM, Raymond Hettinger wrote: >> >>> [Barry Warsaw] >>>> So, we need to come up with a new release schedule for Python 3.0. >>>> My suggestion: >>>> 15-Oct-2008 3.0 beta 4 >>>> 05-Nov-2008 3.0 rc 2 >>>> 19-Nov-2008 3.0 rc 3 >>>> 03-Dec-2008 3.0 final >>>> Given what still needs to be done, is this a reasonable schedule? >>>> Do we need two more betas? >> >>> Yes to both questions. >> >> I think that's contradictory :). If we need two betas, then 05-Nov >> becomes beta 5, 19-Nov is rc 2. If we don't need another rc then >> we can >> still do a final release on 03-Dec, otherwise we probably go 2 weeks >> later. I don't want to go much later than that though because then >> we >> get into the holiday season. > > Do we need the full two weeks between rc's? Or is it too much of a > pain > to cut releases 3 weeks in a row? > > E.g. something like: > > 15-Oct-2008 3.0 beta 4 > 05-Nov-2008 3.0 beta 5 > 19-Nov-2008 3.0 rc 2 > 26-Nov-2008 3.0 rc 3 (if needed) > 03-Dec-2008 3.0 final I won't be able to cut another release between the 15th and 5th, so at least that one should be 2 weeks. If we don't need the additional rc, then we can release early, which would put us just before the US Thanksgiving holiday. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOvcQ3EjvBPtnXfVAQK5mwP9GQfw3zNvGhJWiSkZ2gQ1LNr0rnmfVmpF WcDePkz3e5nsOjtkwiN0rlYHIQE9ySPfvtqqrInBW8y97y79mTjiM4S32XHLyAsd WEWRb0ClcLuZs+JveAb8KF5pO0RlDgX9Dd6puuPr8kGa5aN/rosfsnXra1GrYpj3 JQghQ89JNkE= =+Ymq -----END PGP SIGNATURE-----
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