Re: [python-committers] Policy for committing to 2.7

2013-06-22 Thread Nick Coghlan
On 23 June 2013 12:56, Benjamin Peterson wrote: > 2013/6/22 Eli Bendersky : >> Yes, this makes sense too. >> >> In general there seems to be an agreement, so it would be great to document >> in some place. Many years will pass before we have another "special" release >> like Python 2.7, so it's wo

Re: [python-committers] Policy for committing to 2.7

2013-06-22 Thread Benjamin Peterson
2013/6/22 Eli Bendersky : > Yes, this makes sense too. > > In general there seems to be an agreement, so it would be great to document > in some place. Many years will pass before we have another "special" release > like Python 2.7, so it's worth spending an extra few minutes to have this > written

Re: [python-committers] Policy for committing to 2.7

2013-06-22 Thread Anthony Baxter
Maybe time it so when we *would* have released a 2.8 (18 months or so after 2.7) is when it goes into critical/security fixes only? On Jun 22, 2013 11:50 PM, "Eli Bendersky" wrote: > > > > On Sat, Jun 22, 2013 at 12:35 PM, Barry Warsaw wrote: > >> On Jun 22, 2013, at 12:02 PM, Eli Bendersky wrot

Re: [python-committers] Policy for committing to 2.7

2013-06-22 Thread Guido van Rossum
On Sat, Jun 22, 2013 at 12:35 PM, Barry Warsaw wrote: > [1] Well, maybe penultimate, but I wouldn't mind seeing the Mercurial > equivalent of a wrastlin' match between him and the BDFL. :) You wouldn't see that this summer though -- I could just tackle him in the office. :-) -- --Guido van Ross

Re: [python-committers] Policy for committing to 2.7

2013-06-22 Thread Eli Bendersky
On Sat, Jun 22, 2013 at 12:35 PM, Barry Warsaw wrote: > On Jun 22, 2013, at 12:02 PM, Eli Bendersky wrote: > > >I may be missing something, but do we have a policy of what we're supposed > >to commit to the 2.7 branch at this point? I was under the impression that > >it's only bug fixes, document

Re: [python-committers] Policy for committing to 2.7

2013-06-22 Thread R. David Murray
On Sat, 22 Jun 2013 15:35:41 -0400, Barry Warsaw wrote: > On Jun 22, 2013, at 12:02 PM, Eli Bendersky wrote: > > >I may be missing something, but do we have a policy of what we're supposed > >to commit to the 2.7 branch at this point? I was under the impression that > >it's only bug fixes, docume

Re: [python-committers] Policy for committing to 2.7

2013-06-22 Thread Barry Warsaw
On Jun 22, 2013, at 12:02 PM, Eli Bendersky wrote: >I may be missing something, but do we have a policy of what we're supposed >to commit to the 2.7 branch at this point? I was under the impression that >it's only bug fixes, documentation, and maybe tests. But it seems that >there are developers w

Re: [python-committers] Policy for committing to 2.7

2013-06-22 Thread Antoine Pitrou
Le samedi 22 juin 2013 à 12:02 -0700, Eli Bendersky a écrit : > Hello, > > > I may be missing something, but do we have a policy of what we're > supposed to commit to the 2.7 branch at this point? I was under the > impression that it's only bug fixes, documentation, and maybe tests. > But it seem

[python-committers] Policy for committing to 2.7

2013-06-22 Thread Eli Bendersky
Hello, I may be missing something, but do we have a policy of what we're supposed to commit to the 2.7 branch at this point? I was under the impression that it's only bug fixes, documentation, and maybe tests. But it seems that there are developers who see it otherwise. For example, Raymond's cha