On 8/5/2010 2:19 AM, Georg Brandl wrote:
> Am 05.08.2010 01:26, schrieb Barry Warsaw:
>> On Aug 04, 2010, at 06:39 PM, Steve Holden wrote:
>>
>>> I'll see if I can get God to extend it for you.
>>
>> No need to involve the supernatural Steve! Just approve that PSF grant I
>> submitted so I can fin
On Wed, Aug 04, 2010 at 07:26:06PM -0400, Barry Warsaw wrote:
> On Aug 04, 2010, at 06:39 PM, Steve Holden wrote:
> >I'll see if I can get God to extend it for you.
>
> No need to involve the supernatural Steve! Just approve that PSF grant I
> submitted so I can finish my (Python powered of cours
Am 05.08.2010 01:26, schrieb Barry Warsaw:
> On Aug 04, 2010, at 06:39 PM, Steve Holden wrote:
>
>>I'll see if I can get God to extend it for you.
>
> No need to involve the supernatural Steve! Just approve that PSF grant I
> submitted so I can finish my (Python powered of course!) clone army.
>> If you mean to imply that a release manager should care for the stability
>> of "their" branch also in between of releases -- I'd love to do that,
>> but I'd need a 36-hour day then.
>>
> I'll see if I can get God to extend it for you. I honestly do understand
> that everyone else works under th
Steve Holden writes:
> But I see rules being established ("there's a language moratorium: no
> changes!", "no release should be made unless the buildbots are *all*
> green") and then ignored apparently on a whim. This doesn't give people
> any confidence that the rules actually mean much, and
On Aug 04, 2010, at 06:39 PM, Steve Holden wrote:
>I'll see if I can get God to extend it for you.
No need to involve the supernatural Steve! Just approve that PSF grant I
submitted so I can finish my (Python powered of course!) clone army.
>I honestly do understand that everyone else works und
On 8/4/2010 6:11 PM, Georg Brandl wrote:
> Am 04.08.2010 19:56, schrieb Steve Holden:
>
>> This whole discussion seems to make it clear that the release manager
>> procedures are still ill-defined in certain areas.
>
> If you mean to imply that a release manager should care for the stability
> of
Am 04.08.2010 19:56, schrieb Steve Holden:
> This whole discussion seems to make it clear that the release manager
> procedures are still ill-defined in certain areas.
If you mean to imply that a release manager should care for the stability
of "their" branch also in between of releases -- I'd lo
Am 04.08.2010 20:25, schrieb Barry Warsaw:
> On Aug 04, 2010, at 01:56 PM, Steve Holden wrote:
>
>>But I see rules being established ("there's a language moratorium: no
>>changes!", "no release should be made unless the buildbots are *all*
>>green") and then ignored apparently on a whim. This does
On Wed, 04 Aug 2010 23:53:22 +0200
Georg Brandl wrote:
> >
> > The hard part is to know *when* to look. As you might have noticed, the
> > Python test suite does not run in ten seconds, especially on some of the
> > buildbots -- it can take 1-2 there to complete.
>
> That should be "1-2 hours",
Am 04.08.2010 17:53, schrieb Georg Brandl:
> Am 04.08.2010 17:15, schrieb exar...@twistedmatrix.com:
>> On 02:51 pm, ba...@python.org wrote:
>>>On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state af
On 8/4/2010 2:57 PM, "Martin v. Löwis" wrote:
>> This whole discussion seems to make it clear that the release manager
>> procedures are still ill-defined in certain areas.
>
> No. It rather makes clear that people who never had the role of release
> manager
>
>> Otherwise a release
>> manager co
Georg Brandl wrote:
> The hard part is to know *when* to look. As you might have noticed, the
> Python test suite does not run in ten seconds, especially on some of the
> buildbots -- it can take 1-2 there to complete.
Based on this and other issues, I don't think it's practical to
expect that p
> This whole discussion seems to make it clear that the release manager
> procedures are still ill-defined in certain areas.
No. It rather makes clear that people who never had the role of release
manager
> Otherwise a release
> manager could proceed by reading a web page an even, heaven help us,
On Aug 04, 2010, at 01:56 PM, Steve Holden wrote:
>But I see rules being established ("there's a language moratorium: no
>changes!", "no release should be made unless the buildbots are *all*
>green") and then ignored apparently on a whim. This doesn't give people
>any confidence that the rules act
On Wed, 04 Aug 2010 13:56:27 -0400
Steve Holden wrote:
>
> This whole discussion seems to make it clear that the release manager
> procedures are still ill-defined in certain areas. Otherwise a release
> manager could proceed by reading a web page an even, heaven help us,
> following specific lin
Wiadomość napisana przez Steve Holden w dniu 2010-08-04, o godz. 19:56:
> But I see rules being established ("there's a language moratorium: no
> changes!", "no release should be made unless the buildbots are *all*
> green") and then ignored apparently on a whim. This doesn't give people
> any co
On 8/4/2010 12:42 PM, exar...@twistedmatrix.com wrote:
> On 03:31 pm, ba...@python.org wrote:
>> On Aug 04, 2010, at 03:15 PM, exar...@twistedmatrix.com wrote:
>>> On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
> I think the issue is that many core
On Aug 04, 2010, at 06:58 PM, Antoine Pitrou wrote:
>On Wed, 04 Aug 2010 16:45:37 -
>exar...@twistedmatrix.com wrote:
>>
>> I don't think it's that hard to take a look at the end of the day
>> (or before starting anything else the next morning). All it really
>> takes is a choice on the part
Am 04.08.2010 18:21, schrieb David Stanek:
> On Wed, Aug 4, 2010 at 11:53 AM, Georg Brandl wrote:
>>
>> The hard part is to know *when* to look. As you might have noticed, the
>> Python test suite does not run in ten seconds, especially on some of the
>> buildbots -- it can take 1-2 there to comp
Am 04.08.2010 18:45, schrieb exar...@twistedmatrix.com:
>>>How hard is it to look at a web page?
>>
>>The hard part is to know *when* to look. As you might have noticed,
>>the
>>Python test suite does not run in ten seconds, especially on some of
>>the
>>buildbots -- it can take 1-2 there to com
On Wed, 04 Aug 2010 16:45:37 -
exar...@twistedmatrix.com wrote:
>
> I don't think it's that hard to take a look at the end of the day (or
> before starting anything else the next morning). All it really takes is
> a choice on the part of each developer to care whether or not their
> change
On 03:53 pm, g.bra...@gmx.net wrote:
Am 04.08.2010 17:15, schrieb exar...@twistedmatrix.com:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit s
On 03:31 pm, ba...@python.org wrote:
On Aug 04, 2010, at 03:15 PM, exar...@twistedmatrix.com wrote:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they c
On Wed, Aug 4, 2010 at 11:53 AM, Georg Brandl wrote:
>
> The hard part is to know *when* to look. As you might have noticed, the
> Python test suite does not run in ten seconds, especially on some of the
> buildbots -- it can take 1-2 there to complete. So if you look too soon,
> you won't see a
Am 04.08.2010 17:15, schrieb exar...@twistedmatrix.com:
> On 02:51 pm, ba...@python.org wrote:
>>On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
>>>I think the issue is that many core developers don't have the reflex
>>>to check buildbot state after they commit some changes (or at least
>>>on a
On 03:17 pm, fuzzy...@voidspace.org.uk wrote:
On 04/08/2010 16:15, exar...@twistedmatrix.com wrote:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they c
On Aug 04, 2010, at 03:15 PM, exar...@twistedmatrix.com wrote:
>On 02:51 pm, ba...@python.org wrote:
>>On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
>>>I think the issue is that many core developers don't have the reflex
>>>to check buildbot state after they commit some changes (or at least
On 04/08/2010 16:15, exar...@twistedmatrix.com wrote:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit some changes (or at least
on a regular, s
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit some changes (or at least
on a regular, say weekly, basis), and so gradually the buildbots have
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
>I think the issue is that many core developers don't have the reflex
>to check buildbot state after they commit some changes (or at least
>on a regular, say weekly, basis), and so gradually the buildbots have
>a tendency to turn from green to re
On 8/4/2010 6:08 AM, Nick Coghlan wrote:
> On Wed, Aug 4, 2010 at 7:42 PM, Dirkjan Ochtman wrote:
>> On Wed, Aug 4, 2010 at 11:16, Antoine Pitrou wrote:
>>> I would advocate a system were people are encouraged to take
>>> responsibility of the problems they introduce when committing changes.
>>>
On Wed, Aug 4, 2010 at 7:42 PM, Dirkjan Ochtman wrote:
> On Wed, Aug 4, 2010 at 11:16, Antoine Pitrou wrote:
>> I would advocate a system were people are encouraged to take
>> responsibility of the problems they introduce when committing changes.
>> Of course, there are sometimes situations where
On Wed, Aug 4, 2010 at 11:16, Antoine Pitrou wrote:
> I would advocate a system were people are encouraged to take
> responsibility of the problems they introduce when committing changes.
> Of course, there are sometimes situations where it's not possible
> (triggering platform-specific oddities,
34 matches
Mail list logo
