Re: RELEASED Python 2.5.2, release candidate 1

On Feb 15, 2008 11:27 AM, Terry Reedy <[EMAIL PROTECTED]> wrote: > 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. -- http://ma

Re: RELEASED Python 2.5.2, release candidate 1

On 14 feb, 22:39, Paul Rubin wrote: > 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 understo

Re: RELEASED Python 2.5.2, release candidate 1

Paul Rubin wrote: > I join everyone else in thanking Martin for his work on this whole > effort. This wording and naming thing is a trivial subtopic. Ditto! The list of fixes is impressive. Kudos to everyone who everyone responsible for the changes, and for keeping them organized and document

Re: RELEASED Python 2.5.2, release candidate 1

Jeff Schwab <[EMAIL PROTECTED]> writes: > > 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_VERSI

Re: RELEASED Python 2.5.2, release candidate 1

Carl Banks wrote: > On Feb 14, 6:16 pm, "Martin v. Löwis" <[EMAIL PROTECTED]> 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

Re: RELEASED Python 2.5.2, release candidate 1

"Terry Reedy" <[EMAIL PROTECTED]> writes: > "Ben Finney" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > | 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 b

Re: RELEASED Python 2.5.2, release candidate 1

"Ben Finney" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] | 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.

Re: RELEASED Python 2.5.2, release candidate 1

On Feb 14, 6:16 pm, "Martin v. Löwis" <[EMAIL PROTECTED]> 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* o

Re: RELEASED Python 2.5.2, release candidate 1

Ben Finney <[EMAIL PROTECTED]> writes: > "Martin v. Löwis" <[EMAIL PROTECTED]> writes: > > 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 > > ava

Re: RELEASED Python 2.5.2, release candidate 1

Paul Rubin writes: > I thought the original announcement text was fine, but that may be > because I'm accustomed to the Python release cycle including the RC > releases. I think it's needlessly confusing to refer to a "release candidate release"; that's almost an oxymor

Re: RELEASED Python 2.5.2, release candidate 1

"Martin v. Löwis" <[EMAIL PROTECTED]> writes: > Please accept my apologies. Thanks, but not needed. I'm merely trying to address the confusing terminology in this announcement and future ones. > I'm not a native speaker, so "to release" means to me what the > dictionary says it means: m-w's four

Re: RELEASED Python 2.5.2, release candidate 1

"Martin v. Löwis" <[EMAIL PROTECTED]> writes: > >> happy to announce the release of Python 2.5.2 (release candidate 1). > So is the subject incorrect as well? If so, what should it say? Neither place is technically incorrect, but both are written in a way that could give a slightly wrong impressi

Re: RELEASED Python 2.5.2, release candidate 1

Ben Finney wrote: > "Martin v. Löwis" <[EMAIL PROTECTED]> writes: > >> 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

Re: RELEASED Python 2.5.2, release candidate 1

>> 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 "relea

Re: RELEASED Python 2.5.2, release candidate 1

"Martin v. Löwis" <[EMAIL PROTECTED]> writes: > 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 announc

Re: RELEASED Python 2.5.2, release candidate 1

> The Mac binary is giving a 404. Thanks for pointing that out - it's fixed now. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list

Re: RELEASED Python 2.5.2, release candidate 1

The Mac binary is giving a 404. When/if it's supposed to work, will it upgrade the Leopard standard framework install, or will we need to mess around with the PATH? -- http://mail.python.org/mailman/listinfo/python-list

RELEASED Python 2.5.2, release candidate 1

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