Mailing List Archive: Python: Dev

thinking about 2.7

1 2

View All

Index | Next | Previous | View Threaded

benjamin at python

Sep 23, 2009, 7:35 AM

Post #1 of 29 (1031 views)
Permalink

thinking about 2.7

Hi everyone,
I've started plotting the release of 2.7. I'd like to try for a final
release mid next summer. 3.2 should be released, if not at the same
time as 2.7, within a few weeks to avoid 2.x having features which 3.x
doesn't. If no one has problems with this, I will draft a schedule.

Are we still planning to make 3.3 the main development focus and start
the 5 years of 2.x maintenance after this release?

Additionally, I'm very apprehensive about doing any kind of release
without the buildbots running. Does anyone know when they might be up?

--
Regards,
Benjamin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

exarkun at twistedmatrix

Sep 23, 2009, 8:13 AM

Post #2 of 29 (995 views)
Permalink

Re: thinking about 2.7 [In reply to]

On 02:35 pm, benjamin [at] python wrote:
>Hi everyone,
>I've started plotting the release of 2.7. I'd like to try for a final
>release mid next summer. 3.2 should be released, if not at the same
>time as 2.7, within a few weeks to avoid 2.x having features which 3.x
>doesn't. If no one has problems with this, I will draft a schedule.
>
>Are we still planning to make 3.3 the main development focus and start
>the 5 years of 2.x maintenance after this release?

I hope that this decision will be delayed until the release is closer,
so that it can be based on how 3.x adoption is progressing.
>Additionally, I'm very apprehensive about doing any kind of release
>without the buildbots running. Does anyone know when they might be up?

I was planning on replying to Antoine's earlier message about the
buildbots after a sufficiently long silence. I'll reply here instead.

Quite a few years of experience with a distributed team of build slave
managers has shown me that by far the most reliable way to keep slaves
online is to have them managed by a dedicated team. This team doesn't
need to be small, but since finding dedicated people can sometimes be
challenging, I think small teams are the most likely outcome (possibly
resulting in a team of one). Adding more people who are only mildly
interested doesn't help. If, as I believe is the case with Python's
buildbot configuration, the mildly interested people have sole control
over certain slaves, then it is actually detrimental.

It's easy for someone to volunteer to set up a new slave. It's even
easy to make sure it keeps running for 6 months. But it's not as easy
to keep it running indefinitely. This isn't about the software involved
(at least not entirely). It's about someone paying attention to whether
the slave restarts on reboots, and about paying attention to whether the
slave host has lots its network connection, or been decomissioned, or
whether a system upgrade disabled the slave, or whatever other random
administrative-like tasks are necessary to keep things running. Casual
volunteers generally just won't keep up with these tasks.

I suggest finding someone who's seriously interested in the quality of
CPython and giving them the responsibility of keeping things operating
properly. This includes paying attention to the status of slaves,
cajoling hardware operators into bringing hosts back online and fixing
network issues, and finding replacements of the appropriate type
(hardware/software platform) when a slave host is permanently lost.

I would also personally recommend that this person first (well, after
tracking down all the slave operators and convincing them to bring their
slaves back online) acquire shell access to all of the slave machines so
that the owners of the slave hosts themselves no longer need to be the
gating factor for most issues.

Jean-Paul
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

fuzzyman at voidspace

Sep 23, 2009, 8:36 AM

Post #3 of 29 (996 views)
Permalink

Re: thinking about 2.7 [In reply to]

Benjamin Peterson wrote:
> Hi everyone,
> I've started plotting the release of 2.7. I'd like to try for a final
> release mid next summer. 3.2 should be released, if not at the same
> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
> doesn't. If no one has problems with this, I will draft a schedule.
>
+1

I'm keen to see a 2.7 release as there are good new features on trunk
(particularly in unittest :-)

Michael

> Are we still planning to make 3.3 the main development focus and start
> the 5 years of 2.x maintenance after this release?
>
> Additionally, I'm very apprehensive about doing any kind of release
> without the buildbots running. Does anyone know when they might be up?
>
>

--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

solipsis at pitrou

Sep 23, 2009, 9:29 AM

Post #4 of 29 (1000 views)
Permalink

Re: thinking about 2.7 [In reply to]

Benjamin Peterson <benjamin <at> python.org> writes:
>
> Hi everyone,
> I've started plotting the release of 2.7. I'd like to try for a final
> release mid next summer. 3.2 should be released, if not at the same
> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
> doesn't. If no one has problems with this, I will draft a schedule.

If you want to avoid the low-activity low-responsiveness holiday period, you
might shoot for June or September/October instead.

Regards

Antoine.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

brett at python

Sep 23, 2009, 11:03 AM

Post #5 of 29 (993 views)
Permalink

Re: thinking about 2.7 [In reply to]

On Wed, Sep 23, 2009 at 07:35, Benjamin Peterson <benjamin [at] python> wrote:
> Hi everyone,
> I've started plotting the release of 2.7. I'd like to try for a final
> release mid next summer. 3.2 should be released, if not at the same
> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
> doesn't. If no one has problems with this, I will draft a schedule.
>

Yes. Does this mean you are volunteering to be the 3.2 release
manager? Or simply prodding for volunteers? If it's the former are you
at all worried about burn-out from doing two release so close together
and being on the hook for two point releases at roughly the same time
for about two years after?

> Are we still planning to make 3.3 the main development focus and start
> the 5 years of 2.x maintenance after this release?

I think so. As Jean-Paul somewhat pointed out the decision can change,
but at this point I know I am willing to say that I don't want to have
to port to four branches anymore if I don't need to.

>
> Additionally, I'm very apprehensive about doing any kind of release
> without the buildbots running. Does anyone know when they might be up?

I don't know the answer, but it might be "never". We used to do
releases without them, so it's not impossible. Just means you have to
really push the alphas, betas, and RCs.

Titus Brown is actually working on a buildbot alternative that's more
volunteer-friendly (pony-build). Hopefully that will be up and going
by then so we can contemplate using that.

-Brett
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

exarkun at twistedmatrix

Sep 23, 2009, 11:24 AM

Post #6 of 29 (993 views)
Permalink

Re: thinking about 2.7 [In reply to]

On 06:03 pm, brett [at] python wrote:
>On Wed, Sep 23, 2009 at 07:35, Benjamin Peterson <benjamin [at] python>
>wrote:
>[snip]
>>
>>Additionally, I'm very apprehensive about doing any kind of release
>>without the buildbots running. Does anyone know when they might be up?
>
>I don't know the answer, but it might be "never". We used to do
>releases without them, so it's not impossible. Just means you have to
>really push the alphas, betas, and RCs.
>
>Titus Brown is actually working on a buildbot alternative that's more
>volunteer-friendly (pony-build). Hopefully that will be up and going
>by then so we can contemplate using that.

I certainly wish Titus luck in his project, but I'm skeptical about
pony-build magically fixing the problems CPython development has with
buildbot.

Jean-Paul
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

benjamin at python

Sep 23, 2009, 1:21 PM

Post #7 of 29 (990 views)
Permalink

Re: thinking about 2.7 [In reply to]

2009/9/23 Antoine Pitrou <solipsis [at] pitrou>:
> Benjamin Peterson <benjamin <at> python.org> writes:
>>
>> Hi everyone,
>> I've started plotting the release of 2.7. I'd like to try for a final
>> release mid next summer. 3.2 should be released, if not at the same
>> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
>> doesn't. If no one has problems with this, I will draft a schedule.
>
> If you want to avoid the low-activity low-responsiveness holiday period, you
> might shoot for June or September/October instead.

That is a good point, so I think we should shoot for June.

--
Regards,
Benjamin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

benjamin at python

Sep 23, 2009, 1:34 PM

Post #8 of 29 (990 views)
Permalink

Re: thinking about 2.7 [In reply to]

2009/9/23 Brett Cannon <brett [at] python>:
> On Wed, Sep 23, 2009 at 07:35, Benjamin Peterson <benjamin [at] python> wrote:
>> Hi everyone,
>> I've started plotting the release of 2.7. I'd like to try for a final
>> release mid next summer. 3.2 should be released, if not at the same
>> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
>> doesn't. If no one has problems with this, I will draft a schedule.
>>
>
> Yes. Does this mean you are volunteering to be the 3.2 release
> manager? Or simply prodding for volunteers? If it's the former are you
> at all worried about burn-out from doing two release so close together
> and being on the hook for two point releases at roughly the same time
> for about two years after?

While I certainly wouldn't mind doing only 2.7, I don't know how we
could preserve everyone's sanity and release them at about the same
time. Different RMs would have different times they can do releases,
so I would worry about there being a release in a slightly different
stage of a different branch every couple weeks.

As for burn out, I expected 2.7.x, as the last 2.x release, to be
different in that several people would do the maintenance releases
(perhaps on a 6 month schedule or so) for the 5 year period, so that
would leave me with just 3.2.x (and maybe another 3.1.x release).

...
>>
>> Additionally, I'm very apprehensive about doing any kind of release
>> without the buildbots running. Does anyone know when they might be up?
>
> I don't know the answer, but it might be "never". We used to do
> releases without them, so it's not impossible. Just means you have to
> really push the alphas, betas, and RCs.

What do you mean "push"?

--
Regards,
Benjamin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

brett at python

Sep 23, 2009, 2:12 PM

Post #9 of 29 (985 views)
Permalink

Re: thinking about 2.7 [In reply to]

On Wed, Sep 23, 2009 at 13:34, Benjamin Peterson <benjamin [at] python> wrote:
> 2009/9/23 Brett Cannon <brett [at] python>:
>> On Wed, Sep 23, 2009 at 07:35, Benjamin Peterson <benjamin [at] python> wrote:
>>> Hi everyone,
>>> I've started plotting the release of 2.7. I'd like to try for a final
>>> release mid next summer. 3.2 should be released, if not at the same
>>> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
>>> doesn't. If no one has problems with this, I will draft a schedule.
>>>
>>
>> Yes. Does this mean you are volunteering to be the 3.2 release
>> manager? Or simply prodding for volunteers? If it's the former are you
>> at all worried about burn-out from doing two release so close together
>> and being on the hook for two point releases at roughly the same time
>> for about two years after?
>
> While I certainly wouldn't mind doing only 2.7, I don't know how we
> could preserve everyone's sanity and release them at about the same
> time. Different RMs would have different times they can do releases,
> so I would worry about there being a release in a slightly different
> stage of a different branch every couple weeks.
>

If you are okay with it then that's fine.

> As for burn out, I expected 2.7.x, as the last 2.x release, to be
> different in that several people would do the maintenance releases
> (perhaps on a 6 month schedule or so) for the 5 year period, so that
> would leave me with just 3.2.x (and maybe another 3.1.x release).

Well, if you want that to happen you should make that clear now as I
expected you to do the first few micro releases of 2.7.

>
> ...
>>>
>>> Additionally, I'm very apprehensive about doing any kind of release
>>> without the buildbots running. Does anyone know when they might be up?
>>
>> I don't know the answer, but it might be "never". We used to do
>> releases without them, so it's not impossible. Just means you have to
>> really push the alphas, betas, and RCs.
>
> What do you mean "push"?

Promote.

-Brett
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

fuzzyman at voidspace

Sep 23, 2009, 2:19 PM

Post #10 of 29 (985 views)
Permalink

Re: thinking about 2.7 [In reply to]

Benjamin Peterson wrote:
> 2009/9/23 Brett Cannon <brett [at] python>:
>
>> On Wed, Sep 23, 2009 at 07:35, Benjamin Peterson <benjamin [at] python> wrote:
>>
>>> Hi everyone,
>>> I've started plotting the release of 2.7. I'd like to try for a final
>>> release mid next summer. 3.2 should be released, if not at the same
>>> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
>>> doesn't. If no one has problems with this, I will draft a schedule.
>>>
>>>
>> Yes. Does this mean you are volunteering to be the 3.2 release
>> manager? Or simply prodding for volunteers? If it's the former are you
>> at all worried about burn-out from doing two release so close together
>> and being on the hook for two point releases at roughly the same time
>> for about two years after?
>>
>
> While I certainly wouldn't mind doing only 2.7, I don't know how we
> could preserve everyone's sanity and release them at about the same
> time. Different RMs would have different times they can do releases,
> so I would worry about there being a release in a slightly different
> stage of a different branch every couple weeks.
>
> As for burn out, I expected 2.7.x, as the last 2.x release,

Are we definitely decided that 2.7 will be the last major release in the
2.x cycle?

Michael

> to be
> different in that several people would do the maintenance releases
> (perhaps on a 6 month schedule or so) for the 5 year period, so that
> would leave me with just 3.2.x (and maybe another 3.1.x release).
>
> ...
>
>>> Additionally, I'm very apprehensive about doing any kind of release
>>> without the buildbots running. Does anyone know when they might be up?
>>>
>> I don't know the answer, but it might be "never". We used to do
>> releases without them, so it's not impossible. Just means you have to
>> really push the alphas, betas, and RCs.
>>
>
> What do you mean "push"?
>
>
>
>
>
>

--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

brett at python

Sep 23, 2009, 2:27 PM

Post #11 of 29 (985 views)
Permalink

Re: thinking about 2.7 [In reply to]

On Wed, Sep 23, 2009 at 14:19, Michael Foord <fuzzyman [at] voidspace> wrote:
> Benjamin Peterson wrote:
>>
>> 2009/9/23 Brett Cannon <brett [at] python>:
>>
>>>
>>> On Wed, Sep 23, 2009 at 07:35, Benjamin Peterson <benjamin [at] python>
>>> wrote:
>>>
>>>>
>>>> Hi everyone,
>>>> I've started plotting the release of 2.7. I'd like to try for a final
>>>> release mid next summer. 3.2 should be released, if not at the same
>>>> time as 2.7, within a few weeks to avoid 2.x having features which 3.x
>>>> doesn't. If no one has problems with this, I will draft a schedule.
>>>>
>>>>
>>>
>>> Yes. Does this mean you are volunteering to be the 3.2 release
>>> manager? Or simply prodding for volunteers? If it's the former are you
>>> at all worried about burn-out from doing two release so close together
>>> and being on the hook for two point releases at roughly the same time
>>> for about two years after?
>>>
>>
>> While I certainly wouldn't mind doing only 2.7, I don't know how we
>> could preserve everyone's sanity and release them at about the same
>> time. Different RMs would have different times they can do releases,
>> so I would worry about there being a release in a slightly different
>> stage of a different branch every couple weeks.
>>
>> As for burn out, I expected 2.7.x, as the last 2.x release,
>
> Are we definitely decided that 2.7 will be the last major release in the 2.x
> cycle?

I would say we won't be sure until we are closer to release, but I
would be willing to put money down that it will be.

-Brett
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

solipsis at pitrou

Sep 23, 2009, 2:28 PM

Post #12 of 29 (986 views)
Permalink

Re: thinking about 2.7 [In reply to]

Benjamin Peterson <benjamin <at> python.org> writes:
>
> Different RMs would have different times they can do releases,
> so I would worry about there being a release in a slightly different
> stage of a different branch every couple weeks.

Assuming you can do it, +1 for you (Benjamin) being RM for both 2.7 and 3.1.
Indeed, both branches need to be synchronized anyway and the best way to achieve
this is for a single person to overview both of them.

Regards

Antoine.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

benjamin at python

Sep 23, 2009, 2:34 PM

Post #13 of 29 (986 views)
Permalink

Re: thinking about 2.7 [In reply to]

2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
> Benjamin Peterson wrote:
>> As for burn out, I expected 2.7.x, as the last 2.x release,
>
> Are we definitely decided that 2.7 will be the last major release in the 2.x
> cycle?

No, but that's what we're planning for atm.

--
Regards,
Benjamin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

solipsis at pitrou

Sep 23, 2009, 2:36 PM

Post #14 of 29 (986 views)
Permalink

Re: thinking about 2.7 [In reply to]

Michael Foord <fuzzyman <at> voidspace.org.uk> writes:
>
> Are we definitely decided that 2.7 will be the last major release in the
> 2.x cycle?

I don't think any "definitive" decision was made, but judgeing by Benjamin's and
Brett's answers (and by my own sentiment :-)), it certainly is the expectation
of some core developers that we focus primarily on 3.x after 2.7 is released.

Of course, if a large enough number of core developers want to backport stuff to
2.x, they probably can arrange to do so.

Regards

Antoine.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

benjamin at python

Sep 23, 2009, 2:42 PM

Post #15 of 29 (986 views)
Permalink

Re: thinking about 2.7 [In reply to]

2009/9/23 Brett Cannon <brett [at] python>:
> On Wed, Sep 23, 2009 at 13:34, Benjamin Peterson <benjamin [at] python> wrote:
>> As for burn out, I expected 2.7.x, as the last 2.x release, to be
>> different in that several people would do the maintenance releases
>> (perhaps on a 6 month schedule or so) for the 5 year period, so that
>> would leave me with just 3.2.x (and maybe another 3.1.x release).
>
> Well, if you want that to happen you should make that clear now as I
> expected you to do the first few micro releases of 2.7.

I will do the first few 2.7 bug fix releases.

>>>> Additionally, I'm very apprehensive about doing any kind of release
>>>> without the buildbots running. Does anyone know when they might be up?
>>>
>>> I don't know the answer, but it might be "never". We used to do
>>> releases without them, so it's not impossible. Just means you have to
>>> really push the alphas, betas, and RCs.
>>
>> What do you mean "push"?
>
> Promote.

That basically means we will be relying on 3rd party libraries for our
quality control?

--
Regards,
Benjamin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

fuzzyman at voidspace

Sep 23, 2009, 2:52 PM

Post #16 of 29 (986 views)
Permalink

Re: thinking about 2.7 [In reply to]

Benjamin Peterson wrote:
> 2009/9/23 Brett Cannon <brett [at] python>:
>
>> On Wed, Sep 23, 2009 at 13:34, Benjamin Peterson <benjamin [at] python> wrote:
>>
>>> As for burn out, I expected 2.7.x, as the last 2.x release, to be
>>> different in that several people would do the maintenance releases
>>> (perhaps on a 6 month schedule or so) for the 5 year period, so that
>>> would leave me with just 3.2.x (and maybe another 3.1.x release).
>>>
>> Well, if you want that to happen you should make that clear now as I
>> expected you to do the first few micro releases of 2.7.
>>
>
> I will do the first few 2.7 bug fix releases.
>
>
>>>>> Additionally, I'm very apprehensive about doing any kind of release
>>>>> without the buildbots running. Does anyone know when they might be up?
>>>>>
>>>> I don't know the answer, but it might be "never". We used to do
>>>> releases without them, so it's not impossible. Just means you have to
>>>> really push the alphas, betas, and RCs.
>>>>
>>> What do you mean "push"?
>>>
>> Promote.
>>
>
> That basically means we will be relying on 3rd party libraries for our
> quality control?
>
>
>
Isn't that the real compatibility test *anyway* - how successful a new
version of Python is at running all the existing Python code...

Michael

--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

python at rcn

Sep 23, 2009, 4:02 PM

Post #17 of 29 (986 views)
Permalink

Re: thinking about 2.7 [In reply to]

[Michael Foord]
> Are we definitely decided that 2.7 will be the last major release in the
> 2.x cycle?

ISTM, that would depend on the uptake for 3.2.
The users get a say in the matter.

Raymond
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

fuzzyman at voidspace

Sep 23, 2009, 4:05 PM

Post #18 of 29 (987 views)
Permalink

Re: thinking about 2.7 [In reply to]

Raymond Hettinger wrote:
>
> [Michael Foord]
>> Are we definitely decided that 2.7 will be the last major release in
>> the 2.x cycle?
>
> ISTM, that would depend on the uptake for 3.2.
> The users get a say in the matter.
>

That would be my feeling...

Michael

>
> Raymond

--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

benjamin at python

Sep 23, 2009, 4:17 PM

Post #19 of 29 (986 views)
Permalink

Re: thinking about 2.7 [In reply to]

2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
> Isn't that the real compatibility test *anyway* - how successful a new
> version of Python is at running all the existing Python code...

Yes, but we should have expect 3rd party code to be detecting bugs for
us that our test suite could have shown on a platform.

--
Regards,
Benjamin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

fuzzyman at voidspace

Sep 23, 2009, 4:19 PM

Post #20 of 29 (986 views)
Permalink

Re: thinking about 2.7 [In reply to]

Benjamin Peterson wrote:
> 2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
>
>> Isn't that the real compatibility test *anyway* - how successful a new
>> version of Python is at running all the existing Python code...
>>
>
> Yes, but we should have expect 3rd party code to be detecting bugs for
> us that our test suite could have shown on a platform.
>
>
>
Well, Trent Nelson is going to devote some real time to Snakebite - so
there is a very good chance that it will be up and active before the
release. Naturally I agree it would be *preferable* to run tests on all
supported platforms prior to release.

Michael

--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

benjamin at python

Sep 23, 2009, 4:22 PM

Post #21 of 29 (982 views)
Permalink

Re: thinking about 2.7 [In reply to]

2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
> Benjamin Peterson wrote:
>>
>> 2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
>>
>>>
>>> Isn't that the real compatibility test *anyway* - how successful a new
>>> version of Python is at running all the existing Python code...
>>>
>>
>> Yes, but we should have expect 3rd party code to be detecting bugs for
>> us that our test suite could have shown on a platform.
>>
>>
>>
>
> Well, Trent Nelson is going to devote some real time to Snakebite - so there
> is a very good chance that it will be up and active before the release.
> Naturally I agree it would be *preferable* to run tests on all supported
> platforms prior to release.

Could I inquiry about your source of this information?

--
Regards,
Benjamin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

fuzzyman at voidspace

Sep 23, 2009, 4:23 PM

Post #22 of 29 (982 views)
Permalink

Re: thinking about 2.7 [In reply to]

Benjamin Peterson wrote:
> 2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
>
>> Benjamin Peterson wrote:
>>
>>> 2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
>>>
>>>
>>>> Isn't that the real compatibility test *anyway* - how successful a new
>>>> version of Python is at running all the existing Python code...
>>>>
>>>>
>>> Yes, but we should have expect 3rd party code to be detecting bugs for
>>> us that our test suite could have shown on a platform.
>>>
>>>
>>>
>>>
>> Well, Trent Nelson is going to devote some real time to Snakebite - so there
>> is a very good chance that it will be up and active before the release.
>> Naturally I agree it would be *preferable* to run tests on all supported
>> platforms prior to release.
>>
>
> Could I inquiry about your source of this information?
>
>
>
>
From Trent on the snakebite mailing list. Too late for me to look it up
though; an exercise I leave to the reader.

Michael

--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

eric at trueblade

Sep 23, 2009, 5:12 PM

Post #23 of 29 (983 views)
Permalink

Re: thinking about 2.7 [In reply to]

Michael Foord wrote:
> Benjamin Peterson wrote:
>> 2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
>>
>>> Benjamin Peterson wrote:
>>>
>>>> 2009/9/23 Michael Foord <fuzzyman [at] voidspace>:
>>>>
>>>>
>>>>> Isn't that the real compatibility test *anyway* - how successful a new
>>>>> version of Python is at running all the existing Python code...
>>>>>
>>>>>
>>>> Yes, but we should have expect 3rd party code to be detecting bugs for
>>>> us that our test suite could have shown on a platform.
>>>>
>>>>
>>>>
>>>>
>>> Well, Trent Nelson is going to devote some real time to Snakebite -
>>> so there
>>> is a very good chance that it will be up and active before the release.
>>> Naturally I agree it would be *preferable* to run tests on all supported
>>> platforms prior to release.
>>>
>>
>> Could I inquiry about your source of this information?
>>
>>
>>
>>
> From Trent on the snakebite mailing list. Too late for me to look it up
> though; an exercise I leave to the reader.

http://groups.google.com/group/snakebite-list/browse_thread/thread/d08642261f2cc502

Eric.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

ncoghlan at gmail

Sep 23, 2009, 6:48 PM

Post #24 of 29 (971 views)
Permalink

Re: thinking about 2.7 [In reply to]

Eric Smith wrote:
>> From Trent on the snakebite mailing list. Too late for me to look it
>> up though; an exercise I leave to the reader.
>
> http://groups.google.com/group/snakebite-list/browse_thread/thread/d08642261f2cc502

Hmm, I thought I was subscribed to the snakebite list... guess I will
have to check my settings.

Cheers,
Nick.

--
Nick Coghlan | ncoghlan [at] gmail | Brisbane, Australia
---------------------------------------------------------------
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

martin at v

Sep 24, 2009, 4:27 PM

Post #25 of 29 (954 views)
Permalink

Re: thinking about 2.7 [In reply to]

>> Additionally, I'm very apprehensive about doing any kind of release
>> without the buildbots running. Does anyone know when they might be up?

When I (or somebody else) contacts all the slave operators and asks them
to restart the buildbot slaves.

Regards,
Martin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads