The first (and hopefully last) release candidate for Python 2.6.3 is now available via http://www.python.org/download/releases/2.6.3/ Source releases and Windows binaries are currently available, and Mac OS X binaries should be forthcoming. Nearly 100 bugs have been fixed since 2.6.2. Barring any unforeseen problems, we will make the final 2.6.3 release this Friday, October 2nd. Please give this release candidate a spin and let us know if you encounter any show stopping problems. Enjoy, -Barry
Barry Warsaw <barry@python.org> writes:
The first (and hopefully last) release candidate for Python 2.6.3 is now available […]
Thank you for this announcement, and the efforts that go into making this work available. *Especially* thank you for avoiding the oxymoronic “Released: 2.6.3 release candidate” or similar. I hope this signifies a trend toward using the more accurate term “available” for announcing availability of anything that's not an actual release. -- \ “Guaranteed to work throughout its useful life.” —packaging for | `\ clockwork toy, Hong Kong | _o__) | Ben Finney
2009/9/30 Ben Finney <ben+python@benfinney.id.au>:
Barry Warsaw <barry@python.org> writes:
The first (and hopefully last) release candidate for Python 2.6.3 is now available […]
Thank you for this announcement, and the efforts that go into making this work available.
*Especially* thank you for avoiding the oxymoronic “Released: 2.6.3 release candidate” or similar. I hope this signifies a trend toward using the more accurate term “available” for announcing availability of anything that's not an actual release.
Alphas, betas, and release candidates are all releases, too. -- Regards, Benjamin
Benjamin Peterson wrote:
2009/9/30 Ben Finney <ben+python@benfinney.id.au>:
Barry Warsaw <barry@python.org> writes:
The first (and hopefully last) release candidate for Python 2.6.3 is now available […]
Thank you for this announcement, and the efforts that go into making this work available.
*Especially* thank you for avoiding the oxymoronic “Released: 2.6.3 release candidate” or similar. I hope this signifies a trend toward using the more accurate term “available” for announcing availability of anything that's not an actual release.
Alphas, betas, and release candidates are all releases, too.
Not really - they're just key builds that are made available in the lead up to the actual release. Using "<whatever> is available" for the pre-release builds and then "RELEASED: <whatever>" for the actual release as Barry did this time around makes a great deal of sense to me. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia ---------------------------------------------------------------
participants (4)
-
Barry Warsaw -
Ben Finney -
Benjamin Peterson -
Nick Coghlan