Steven D'Aprano wrote:
I've always hated the term "release candidate". It's been released, it is
a release. A release candidate is something which may be released, but
hasn't yet been chosen.
I agree. They are candidates for the final release. Suffix .c1, etc,
instead of .rc1 would be suff
On Wed, 08 Oct 2008 08:19:33 +1100, Ben Finney wrote:
>> I disagree. These say exactly what has happened and tell me what I
>> want to know, which is that something new has been released, which is
>> to say, made available for download.
>
> Which is entirely different from the “release” implicit
On Oct 8, 12:42 am, Ben Finney <[EMAIL PROTECTED]>
wrote:
> "Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>
> > > Is there some policy document or release management guide that could
> > > be updated for release teams to follow on this without needing to have
> > > this discussion every time?
>
> >
[EMAIL PROTECTED] writes:
> Ben> Is there an appropriate email destination for such patches?
>
> You might try [EMAIL PROTECTED]
Thank you.
--
\ “I put contact lenses in my dog's eyes. They had little |
`\ pictures of cats on them. Then I took one out and he ran around |
_
Ben> Is there an appropriate email destination for such patches?
You might try [EMAIL PROTECTED]
--
http://mail.python.org/mailman/listinfo/python-list
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> > Is there some policy document or release management guide that could
> > be updated for release teams to follow on this without needing to have
> > this discussion every time?
>
> It's in PEP 101.
Thank you.
> If it matters to you, please submit
> Is there some policy document or release management guide that could
> be updated for release teams to follow on this without needing to have
> this discussion every time?
It's in PEP 101. If it matters to you, please submit a patch to that
document (which is in subversion) to bugs.python.org. I
Terry Reedy <[EMAIL PROTECTED]> writes:
> Ben Finney wrote:
> > Can I request, in the interest of reducing confusion, that any
> > announcements of pre-release versions of 2.5.3 (or any other
> > Python release) be announced *without* saying “RELEASED: A
> > not-really-release version of Python”.
Ben Finney wrote:
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
Within a few weeks, we will release Python 2.5.3.
I'm glad to see this. Thank you to all involved in the ongoing work of
coordinating Python releases.
Can I request, in the interest of reducing confusion, that any
announcements
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> Within a few weeks, we will release Python 2.5.3.
I'm glad to see this. Thank you to all involved in the ongoing work of
coordinating Python releases.
Can I request, in the interest of reducing confusion, that any
announcements of pre-release versi
10 matches
Mail list logo
