Is there a PEP with end-of-life info?
I had meant to write a PEP on security releases for several
years now. Since this still doesn't exist, here is the outline
of the procedures that maintainers have agreed upon:
- bug fix releases are made until the next feature release is
out (with 2.7 bein
On 10/01/2012 01:30 PM, "Martin v. Löwis" wrote:
Is there a PEP with end-of-life info?
I had meant to write a PEP on security releases for several
years now. Since this still doesn't exist, here is the outline
of the procedures that maintainers have agreed upon:
- bug fix releases are made unti
Le lundi 01 octobre 2012 à 13:30 +0200, "Martin v. Löwis" a écrit :
> I'm not aware of a formal policy for 2.7. I guess it will end its life
> by BDFL pronouncement; giving it a 5 year bug fix period (which would
> end on July 3, 2015) seems a bit long to me - I'd favor to stop bug
> fixing along w
Unfortunately, the list of core developers with the form flag set
doesn't match the actual forms on file. For example, I did not find my
form in the files sent to me by the previous Administrator.
I'm currently in the process of having all the forms scanned. I'll then
check them into the PSF rep
On Oct 01, 2012, at 02:23 PM, Georg Brandl wrote:
>I've now added lifespan information to the 3.2 and 3.3 release schedule
>PEPs, perhaps Barry and Benjamin could do the same for 2.6 to 3.1.
Done for PEP 361, which actually covers both the 2.6 and 3.0 releases. I've
described Python 3.0 as not b
On Oct 01, 2012, at 01:30 PM, Martin v. Löwis wrote:
>I had meant to write a PEP on security releases for several
>years now.
+1
>Since this still doesn't exist, here is the outline
>of the procedures that maintainers have agreed upon:
>- bug fix releases are made until the next feature release
On Oct 01, 2012, at 02:44 PM, Antoine Pitrou wrote:
>"5 years" was once recorded in the 2.7 release page:
>http://mail.python.org/pipermail/python-list/2010-April/573621.html
>
>... although it isn't anymore:
>“Python 2.7 is scheduled to be the last major version in the 2.x series
>before it moves
On 10/1/2012 8:23 AM, Georg Brandl wrote:
On 10/01/2012 01:30 PM, "Martin v. Löwis" wrote:
Is there a PEP with end-of-life info?
I had meant to write a PEP on security releases for several
years now. Since this still doesn't exist, here is the outline
of the procedures that maintainers have ag
On 10/1/2012 1:02 AM, Georg Brandl wrote:
You are right that we should have information about bugfix/security mode
and
about end-of-life; I propose to put them in the respective release schedule
PEPs.
From the commit:
> +3.3 will receive bugfix updates approximately every 4-6 months until
>
On Mon, 01 Oct 2012 10:57:45 -0400, Terry Reedy wrote:
> On 10/1/2012 1:02 AM, Georg Brandl wrote:
>
> > You are right that we should have information about bugfix/security mode
> > and
> > about end-of-life; I propose to put them in the respective release schedule
> > PEPs.
>
> From the commit
On 10/01/2012 04:57 PM, Terry Reedy wrote:
On 10/1/2012 1:02 AM, Georg Brandl wrote:
You are right that we should have information about bugfix/security mode
and
about end-of-life; I propose to put them in the respective release schedule
PEPs.
From the commit:
> +3.3 will receive bugfix
2012/10/1 R. David Murray :
> On the other hand, Gentoo (Arfrever) already found one crasher
> post-release...but fortunately it only happens in debug builds (although
> that could mean there is a behavior bug in non-debug builds).
It definitely happens in release builds.
--
Regards,
Benjamin
_
On 10/01/2012 07:30 PM, Benjamin Peterson wrote:
2012/10/1 R. David Murray :
On the other hand, Gentoo (Arfrever) already found one crasher
post-release...but fortunately it only happens in debug builds (although
that could mean there is a behavior bug in non-debug builds).
It definitely happe
2012/10/1 Georg Brandl :
> I've now added lifespan information to the 3.2 and 3.3 release schedule
> PEPs, perhaps Barry and Benjamin could do the same for 2.6 to 3.1.
I just updated the 3.1 and 2.7 schedules.
--
Regards,
Benjamin
___
python-committer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/12 14:23, Georg Brandl wrote:
> I've now added lifespan information to the 3.2 and 3.3 release
> schedule PEPs, perhaps Barry and Benjamin could do the same for
> 2.6 to 3.1.
http://python.org/dev/peps/pep-0398/
"""
3.3 Lifespan
3.3 will r
On Tue, 02 Oct 2012 01:41:25 +0200, Jesus Cea wrote:
> On 01/10/12 14:23, Georg Brandl wrote:
> > I've now added lifespan information to the 3.2 and 3.3 release
> > schedule PEPs, perhaps Barry and Benjamin could do the same for
> > 2.6 to 3.1.
>
> http://python.org/dev/peps/pep-0398/
>
> """
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/12 02:25, R. David Murray wrote:
>> 3.3 will receive bugfix updates approximately every 4-6 months
>> until one release after the release of 3.4.0 final. After that,
>> security
[...]
> As a native English speaker it is not immediately obviou
On 10/02/2012 02:37 AM, Jesus Cea wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/12 02:25, R. David Murray wrote:
3.3 will receive bugfix updates approximately every 4-6 months
until one release after the release of 3.4.0 final. After that,
security
[...]
As a native English s
18 matches
Mail list logo
