2.5 release schedule
I was hoping to get a lot more feedback about PEP 356 and the 2.5 release schedule. http://www.python.org/peps/pep-0356.html I updated the schedule it is now: alpha 1: May 6, 2006 [planned] alpha 2: June 3, 2006 [planned] alpha 3: July 1, 2006 [planned] beta 1: July 29, 2006 [planned] beta 2: August 26, 2006 [planned] rc 1: September 16, 2006 [planned] final: September 30, 2006 [planned] What do people think about that? There are still a lot of features we want to add. Is this ok with everyone? Do you think it's realistic? We still need a release manager. No one has heard from Anthony. If he isn't interested is someone else interested in trying their hand at it? There are many changes necessary in PEP 101 because since the last release both python and pydotorg have transitioned from CVS to SVN. Creosote also moved. n
On 2/14/06, Neal Norwitz <nnorwitz@gmail.com> wrote:
I was hoping to get a lot more feedback about PEP 356 and the 2.5 release schedule.
http://www.python.org/peps/pep-0356.html
I updated the schedule it is now:
alpha 1: May 6, 2006 [planned] alpha 2: June 3, 2006 [planned] alpha 3: July 1, 2006 [planned] beta 1: July 29, 2006 [planned] beta 2: August 26, 2006 [planned] rc 1: September 16, 2006 [planned] final: September 30, 2006 [planned]
What do people think about that? There are still a lot of features we want to add. Is this ok with everyone? Do you think it's realistic?
Speaking as one of the people who has a PEP to implement, I am okay with it. -Brett
Neal Norwitz wrote:
What do people think about that? There are still a lot of features we want to add. Is this ok with everyone? Do you think it's realistic?
My view on schedules is that they need to exist, whether they are followed or not. So having one is orders of magnitude better than having none. This specific one "looks right" also.
We still need a release manager. No one has heard from Anthony. If he isn't interested is someone else interested in trying their hand at it?
He might be on vacation, no need to worry yet. If he doesn't want to do it, I would. Regards, Martin
On Tue, 2006-02-14 at 21:24 -0800, Neal Norwitz wrote:
We still need a release manager. No one has heard from Anthony. If he isn't interested is someone else interested in trying their hand at it? There are many changes necessary in PEP 101 because since the last release both python and pydotorg have transitioned from CVS to SVN. Creosote also moved.
I would definitely like to see a PEP 101 update as part of the 2.5 RM's responsibilities, and I think it could be done while spinning the first alpha release. I know others have volunteered, but in a pinch I'd be happy to dust off my RM hat and help out too. -Barry
Hi, On Tue, Feb 14, 2006 at 09:24:57PM -0800, Neal Norwitz wrote:
There is at least one SF bug, namely "#1333982 Bugs of the new AST compiler", that in my humble opinion absolutely needs to be fixed before the release, even though I won't hide that I have no intention of fixing it myself. Should I raise the issue here in python-dev, and see if we agree that it is critical? (Sorry if I should know about the procedure. Does it then go in the PEP's Planned Features list?) A bientot, Armin
It is critical, but I hadn't seen the bug report. Feel free to assign AST bugs to me and assign them a > 5 priority. Jeremy On 2/17/06, Armin Rigo <arigo@tunes.org> wrote:
Hi,
On Tue, Feb 14, 2006 at 09:24:57PM -0800, Neal Norwitz wrote:
There is at least one SF bug, namely "#1333982 Bugs of the new AST compiler", that in my humble opinion absolutely needs to be fixed before the release, even though I won't hide that I have no intention of fixing it myself. Should I raise the issue here in python-dev, and see if we agree that it is critical?
(Sorry if I should know about the procedure. Does it then go in the PEP's Planned Features list?)
A bientot,
Armin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/jeremy%40alum.mit.edu
Actually, it might be easier to assign separate bugs. A number of the old bugs appear to have been fixed. It's hard to track individual items within a bug report. Jeremy On 2/17/06, Jeremy Hylton <jeremy@alum.mit.edu> wrote:
It is critical, but I hadn't seen the bug report. Feel free to assign AST bugs to me and assign them a > 5 priority.
Jeremy
On 2/17/06, Armin Rigo <arigo@tunes.org> wrote:
Hi,
On Tue, Feb 14, 2006 at 09:24:57PM -0800, Neal Norwitz wrote:
There is at least one SF bug, namely "#1333982 Bugs of the new AST compiler", that in my humble opinion absolutely needs to be fixed before the release, even though I won't hide that I have no intention of fixing it myself. Should I raise the issue here in python-dev, and see if we agree that it is critical?
(Sorry if I should know about the procedure. Does it then go in the PEP's Planned Features list?)
A bientot,
Armin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/jeremy%40alum.mit.edu
On 2/17/06, Armin Rigo <arigo@tunes.org> wrote:
Hi,
On Tue, Feb 14, 2006 at 09:24:57PM -0800, Neal Norwitz wrote:
There is at least one SF bug, namely "#1333982 Bugs of the new AST compiler", that in my humble opinion absolutely needs to be fixed before the release, even though I won't hide that I have no intention of fixing it myself. Should I raise the issue here in python-dev, and see if we agree that it is critical?
I agree it's critical.
(Sorry if I should know about the procedure. Does it then go in the PEP's Planned Features list?)
I don't think it belongs in the PEP. I bumped the priority to 7 which is the standard protocol, though I don't know that it's really followed. I will enumerate the existing problems for Jeremy in the bug report. In the future, I would also prefer separate bug reports. Feel free to assign new bugs to Jeremy too. :-) n
Hi Neal & Jeremy, On Fri, Feb 17, 2006 at 10:53:19PM -0800, Neal Norwitz wrote:
I don't think it belongs in the PEP. I bumped the priority to 7 which is the standard protocol, though I don't know that it's really followed.
Ok.
I will enumerate the existing problems for Jeremy in the bug report.
In the future, I would also prefer separate bug reports. Feel free to assign new bugs to Jeremy too. :-)
Thanks :-) A bientot, Armin
participants (7)
-
"Martin v. Löwis"
-
Armin Rigo
-
Barry Warsaw
-
Brett Cannon
-
Jeremy Hylton
-
Neal Norwitz
-
Tony Meyer