RELEASED Python 2.5.2, release candidate 1

Jeff Schwab jeff at
Fri Feb 15 02:24:50 CET 2008

Carl Banks wrote:
> On Feb 14, 6:16 pm, "Martin v. Löwis" <mar... at> wrote:
>>>> 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_VERSION-RELEASE) is a different beast 
from a release candidate (PRODUCT_VERSION-RC1).

More information about the Python-list mailing list