"John Salerno" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Why would 2.4.4 come out after the final release of 2.5?
Code patches are generally applied first to the development branch. Those
that merely fix bugs usually get backported to the maintenance branch.*
Releasing 2.4
Fredrik Lundh wrote:
> John Salerno wrote:
>
>>> Assuming no major bugs pop up, the next release of Python will
>>> be Python 2.5 (alpha 1), with a final 2.4.4 release of Python
>>> shortly after the final version of Python 2.5.
>> Why would 2.4.4 come out after the final release of 2.5?
>
> the
John Salerno wrote:
> > Assuming no major bugs pop up, the next release of Python will
> > be Python 2.5 (alpha 1), with a final 2.4.4 release of Python
> > shortly after the final version of Python 2.5.
>
> Why would 2.4.4 come out after the final release of 2.5?
the 2.X.Y releases are bugfix re
John Salerno wrote:
> Anthony Baxter wrote:
>>On behalf of the Python development team and the Python community,
>>I'm happy to announce the release of Python 2.4.3 (final).
>
> Thanks!
>
>>Assuming no major bugs pop up, the next release of Python will
>>be Python 2.5 (alpha 1), with a final 2.4.
Anthony Baxter wrote:
> On behalf of the Python development team and the Python community,
> I'm happy to announce the release of Python 2.4.3 (final).
Thanks!
> Assuming no major bugs pop up, the next release of Python will
> be Python 2.5 (alpha 1), with a final 2.4.4 release of Python
> shor
On behalf of the Python development team and the Python community,
I'm happy to announce the release of Python 2.4.3 (final).
Python 2.4.3 is a bug-fix release. See the release notes at the
website (also available as Misc/NEWS in the source distribution)
for details of the more than 50 bugs squis
