Ok - we're going to skip the 3rd alpha, and the next release will be
beta1, currently scheduled for June 14th. With all the changes this
week from the needforspeed sprint, cutting a release seems like too
much of a risk.
___
Python-Dev mailing list
Py
Thomas Wouters wrote:
> The fact that much testing goes on between releases
> as well makes the alphas even less important.
I suspect the amount of MS Windows testing done between releases is
fairly small. And what little there is doesn't always use the same
compiler that will eventually be use
Neal Norwitz wrote:
> Anthony's schedule is a bit up in the air which means this schedule
> does not reflect what reality will be. Perhaps we will skip a3
> altogether which will give more time in a sense, though not in reality
> since b1 in that case will hopefully be on or before June 14. FWIW:
Neal Norwitz wrote:
> Anthony's schedule is a bit up in the air which means this schedule
> does not reflect what reality will be. Perhaps we will skip a3
> altogether which will give more time in a sense, though not in reality
> since b1 in that case will hopefully be on or before June 14. FWIW:
Anthony's schedule is a bit up in the air which means this schedule
does not reflect what reality will be. Perhaps we will skip a3
altogether which will give more time in a sense, though not in reality
since b1 in that case will hopefully be on or before June 14. FWIW:
alpha 3: May 25, 2006
On 5/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Thomas> Allow me to pitch in my support for speeding up the releases,Thomas> then. I don't believe alpha releases (of Python) get seriousThomas> testing.Is there nobody else out there that uses Python built from the current svn
re
Thomas> Allow me to pitch in my support for speeding up the releases,
Thomas> then. I don't believe alpha releases (of Python) get serious
Thomas> testing.
Is there nobody else out there that uses Python built from the current svn
repository as the main Python interpreter on a day-to-
On 5/21/06, Aahz <[EMAIL PROTECTED]> wrote:
On Sun, May 21, 2006, Neal Norwitz wrote:> On 5/19/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:Remember, the feature freeze isn't until beta1. New stuff can still go
>>in after the next alpha, before beta1.>> I agree. Of course, it's preferable to ge
Aahz wrote:
> On Sun, May 21, 2006, Neal Norwitz wrote:
>> On 5/19/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
>>> Remember, the feature freeze isn't until beta1. New stuff can still go
>>> in after the next alpha, before beta1.
>> I agree. Of course, it's preferable to get things in ASAP to get
On Sun, May 21, 2006, Neal Norwitz wrote:
> On 5/19/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
>>
>>Remember, the feature freeze isn't until beta1. New stuff can still go
>>in after the next alpha, before beta1.
>
> I agree. Of course, it's preferable to get things in ASAP to get more
> testing
On 5/19/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> Remember, the feature freeze isn't until beta1. New stuff can still go
> in after the next alpha, before beta1.
>
> And pure speedup related items aren't likely to cause feature changes
> (I hope)
I agree. Of course, it's preferable to get th
On Saturday 20 May 2006 08:23, Andrew MacIntyre wrote:
> I'm sorry, but I find such advancing schedules with little warning
> quite objectionable. Particularly the cutoff for new functionality
> implicit in the last of the alphas.
Nonono. Feature freeze is beta1.
Anthony
--
Anthony Baxter <
Remember, the feature freeze isn't until beta1. New stuff can still go
in after the next alpha, before beta1.
And pure speedup related items aren't likely to cause feature changes
(I hope)
Anthony
___
Python-Dev mailing list
Python-Dev@python.org
http
Neal Norwitz wrote:
> I moved up the 2.5 release date by a bit. Ideally, I wanted to have
> the final on July 27 which corresponds to OSCON. This seems too
> aggressive since I haven't updated the schedule publicly. So the new
> schedule has rc1 slated for July 27.
>
> http://www.python.org
Aahz wrote:
>On Thu, May 18, 2006, Neal Norwitz wrote:
>
>
>>I moved up the 2.5 release date by a bit. Ideally, I wanted to have
>>the final on July 27 which corresponds to OSCON. This seems too
>>aggressive since I haven't updated the schedule publicly. So the new
>>schedule has rc1 slated f
On Thu, May 18, 2006, Neal Norwitz wrote:
>
> I moved up the 2.5 release date by a bit. Ideally, I wanted to have
> the final on July 27 which corresponds to OSCON. This seems too
> aggressive since I haven't updated the schedule publicly. So the new
> schedule has rc1 slated for July 27.
>
>
I moved up the 2.5 release date by a bit. Ideally, I wanted to have
the final on July 27 which corresponds to OSCON. This seems too
aggressive since I haven't updated the schedule publicly. So the new
schedule has rc1 slated for July 27.
http://www.python.org/dev/peps/pep-0356/
So far we'v
17 matches
Mail list logo
