RELEASED Python 2.5.2, release candidate 1

[=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=]

On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.5.2 (release candidate 1).

This is the second bugfix release of Python 2.5. Python 2.5 is now in
bugfix-only mode; no new features are being added. According to the
release notes, over 100 bugs and patches have been addressed since
Python 2.5.1, many of them improving the stability of the interpreter,
and improving its portability.

For more information on Python 2.5.2, including download links for
various platforms, release notes, and known issues, please see:

http://www.python.org/2.5.2/

Highlights of this new release include:

Bug fixes. According to the release notes, at least 100 have been fixed.

Highlights of the previous major Python release (2.5) are available
from the Python 2.5 page, at

http://www.python.org/2.5/highlights.html

Enjoy this release,
Martin

Martin v. Loewis
ma****@v.loewis .de
Python Release Manager
(on behalf of the entire python-dev team)

[Carl Banks]

On Feb 14, 6:16 pm, "Martin v. Löwis" <[e-mail] s.dewrote:

On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.5.2 (release candidate 1).

Um. If it's only a release *candidate* of 2.5.2, and not yet a
*release* of 2.5.2, could you please announce it as something other
than a "release"?

It should either be announced as "the release of Python 2.5.2", if
that's the case; or "the availability of the Python 2.5.2 release
candidate 1".

Please accept my apologies. I'm not a native speaker, so "to release"
means to me what the dictionary says it means: m-w's fourth meaning,
"make available to the public". That's what I did - I made the release
candidate available to the public.

So is the subject incorrect as well? If so, what should it say?

I think it's fine as it is. You can "release" a release candidate.
Carl Banks

[Terry Reedy]

"Ben Finney" <bi************ ****@benfinney. id.auwrote in message
news:87******** ****@benfinney. id.au...
| It would be better if it didn't say "released" at all, since (as
| discussed above) this isn't "released" except in the trivial
| always-true sense that it is available.

I think this is slightly picky, but also correct.

| Rather, it might just say "[ANN] Python 2.5.2, release candidate 1".

So I agree, for the future (and no apologies for the present needed), that
this is a slightly better wording.

So, thanks to Martin for trying on the release manager role, and looking
forward to [ANN] Python 2.5.2 released.

tjr

[Ben Finney]

"Terry Reedy" <tj*****@udel.e duwrites:

"Ben Finney" <bi************ ****@benfinney. id.auwrote in message
news:87******** ****@benfinney. id.au...

| Rather, it might just say "[ANN] Python 2.5.2, release candidate 1".

So I agree, for the future (and no apologies for the present
needed), that this is a slightly better wording.

So, thanks to Martin for trying on the release manager role, and
looking forward to [ANN] Python 2.5.2 released.

Agreed on all counts: no apology necessary, address the confusing
wording, and thanks to those doing the often-thankless work of release
management.

--
\ "Smoking cures weight problems. Eventually." -- Steven Wright |
`\ |
_o__) |
Ben Finney

[Jeff Schwab]

Carl Banks wrote:

On Feb 14, 6:16 pm, "Martin v. Löwis" <[e-mail] s.dewrote:

>>>On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.5.2 (release candidate 1).
Um. If it's only a release *candidate* of 2.5.2, and not yet a
*release* of 2.5.2, could you please announce it as something other
than a "release"?
It should either be announced as "the release of Python 2.5.2", if
that's the case; or "the availability of the Python 2.5.2 release
candidate 1".

Please accept my apologies. I'm not a native speaker, so "to release"
means to me what the dictionary says it means: m-w's fourth meaning,
"make available to the public". That's what I did - I made the release
candidate available to the public.

So is the subject incorrect as well? If so, what should it say?

I think it's fine as it is. You can "release" a release candidate.

You can, but it's confusing terminology. In the context of software
development, a release (PRODUCT_VERSIO N-RELEASE) is a different beast
from a release candidate (PRODUCT_VERSIO N-RC1).

[Paul Rubin]

Jeff Schwab <je**@schwabcen ter.comwrites:

I think it's fine as it is. You can "release" a release candidate.

You can, but it's confusing terminology. In the context of software
development, a release (PRODUCT_VERSIO N-RELEASE) is a different beast
from a release candidate (PRODUCT_VERSIO N-RC1).

I agree with this, I think the "release candidate" has indeed been
released in a nontrivial way and should get its own label like
2.5.2-RC1. It has characteristics that a random SVN snapshot doesn't
have, and in some situations there might be reasons to deploy
applications using it (e.g. applications relying on bug fixes that the
RC contains). Therefore the RC has to be labelled and archived for
purposes of tracing problems in any such applications, even if the RC
itself will not receive any support or back-fixes.

I join everyone else in thanking Martin for his work on this whole
effort. This wording and naming thing is a trivial subtopic.

[=?ISO-8859-1?Q?Luis_M._Gonz=E1lez?=]

On 14 feb, 22:39, Paul Rubin <http://phr...@NOSPAM.i nvalidwrote:

I join everyone else in thanking Martin for his work on this whole
effort. This wording and naming thing is a trivial subtopic.

Thanks Martin and company for the good job!
By the way, I'm not a native speaker either and I understood perfectly
the meaning of your post.

Luis

[Anthony Baxter]

On Feb 15, 2008 11:27 AM, Terry Reedy <tj*****@udel.e duwrote:

So, thanks to Martin for trying on the release manager role, and looking
forward to [ANN] Python 2.5.2 released.

Hear, hear! Thanks to Martin for getting this out, and apologies from
me that it didn't happen sooner.