[Python-Dev] [Python-3000] 2.6.1 and 3.0 (original) (raw)
Barry Warsaw barry at python.org
Wed Nov 19 16:17:44 CET 2008
- Previous message: [Python-Dev] [Python-3000] 2.6.1 and 3.0
- Next message: [Python-Dev] [Python-3000] 2.6.1 and 3.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Nov 18, 2008, at 12:46 PM, Georg Brandl wrote:
Barry Warsaw schrieb:
On Nov 18, 2008, at 8:07 AM, Christian Heimes wrote:
Barry Warsaw wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin suggests, and I agree, that we should release Python 3.0 final and 2.6.1 at the same time. Makes sense to me. That would mean that Python 2.6.1 should be ready on 03-Dec (well, if Python 3.0 is ready then!). Should we release 2.6.1rc1, too? Do we need rc's for point releases? I think we did them in the past. There probably never was a significant change between the rc and the final, but Murphy dictates that once you stop doing the rc, the final will be embarrassingly broken :)
True. If the rc's are actually tested and help avoid embarrassment
I'm all for them. If it's just extra work that few will test, then
let's skip them and just do brown bag releases if necessary.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSSQuGHEjvBPtnXfVAQJCfwQAky+ORhR0LaoZ0nevGBkEkl5LZbP0+A4a p0puGCnxuY6DVqx38dJUPLqt+wle+Zw9QX4PhhaalbTWyOQScKQk0p0CxagLnTeG GvlyTQLUM9RxFzolnzcY8mU8ewGnCJp16d7TR40AmMZ/geV/xMDzxL+tPKwiq/5p C4j+VmFHnMU= =EGqf -----END PGP SIGNATURE-----
- Previous message: [Python-Dev] [Python-3000] 2.6.1 and 3.0
- Next message: [Python-Dev] [Python-3000] 2.6.1 and 3.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]