>> In principle, this is fine with me, so go ahead.
>
> Done.
Thanks for looking into these!
Martin
--
http://mail.python.org/mailman/listinfo/python-list
Martin v. Löwis schrieb:
>> I would like to apply fixes for some CVE's which are addressed in 2.5 but not
>> yet in 2.4. this would include
>>
>> CVE-2007-4965
>> CVE-2008-1679
>> CVE-2008-1721
>> CVE-2008-2315
>> CVE-2008-3144
>> CVE-2008-1887
>> CVE-2008-4864
>
> Can you identify the revisions t
> I would like to apply fixes for some CVE's which are addressed in 2.5 but not
> yet in 2.4. this would include
>
> CVE-2007-4965
> CVE-2008-1679
> CVE-2008-1721
> CVE-2008-2315
> CVE-2008-3144
> CVE-2008-1887
> CVE-2008-4864
Can you identify the revisions that would need backporting?
I could o
Martin v. Löwis schrieb:
> Within a few weeks, we will release Python 2.5.3. This will be the last
> bug fix release of Python 2.5, afterwards, future releases of 2.5 will
> only include security fixes, and no binaries (for Windows or OSX) will
> be provided anymore (from python.org).
>
> In princ
Martin,
-On [20081007 09:27], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>Within a few weeks, we will release Python 2.5.3. This will be the last
>bug fix release of Python 2.5, afterwards, future releases of 2.5 will
>only include security fixes, and no binaries (for Windows or OSX) will
>be pr
[EMAIL PROTECTED] wrote:
On Oct 7, 9:27 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
In principle, the release will include all changes that are already on
the release25-maint branch in subversion [1]. If you think that specific
changes should be considered, please create an issue in the bug
[EMAIL PROTECTED] wrote:
> On Oct 7, 9:27 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> In principle, the release will include all changes that are already on
>> the release25-maint branch in subversion [1]. If you think that specific
>> changes should be considered, please create an issue in
On Oct 7, 9:27 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> In principle, the release will include all changes that are already on
> the release25-maint branch in subversion [1]. If you think that specific
> changes should be considered, please create an issue in the bug tracker
> [2], and la
> Just to emphasize this, "changes" means "bugfixes". (I'm mentioning this
> mainly because of the people who joined for 2.6/3.0.) For more info,
> see PEP6 about bugfix releases:
> http://www.python.org/dev/peps/pep-0006/
Thanks for clarifying this. For the last 2.5.x release in particular, we
On Tue, Oct 07, 2008, "Martin v. L?wis" wrote:
>
> In principle, the release will include all changes that are already on
> the release25-maint branch in subversion [1]. If you think that specific
> changes should be considered, please create an issue in the bug tracker
> [2], and label it with th
"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
Within a few weeks, we will release Python 2.5.3. This will be the last
bug fix release of Python 2.5, afterwards, future releases of 2.5 will
only include security fixes, and no binaries (for Windows or OSX) will
be provided anymore (from python.org).
In principle, the release will include all ch
12 matches
Mail list logo
