2010/3/19 Brett Cannon :
> On Thu, Mar 18, 2010 at 20:20, Benjamin Peterson wrote:
>> Pending the resolution of a few Mac OS issues (#8068, #8069, and
>> #8133), I'm not going to tag the release at the moment. Hopefully,
>> we'll still be able to have a release in the next week.
>
> Do you want is
On Thu, Mar 18, 2010 at 20:20, Benjamin Peterson wrote:
> Pending the resolution of a few Mac OS issues (#8068, #8069, and
> #8133), I'm not going to tag the release at the moment. Hopefully,
> we'll still be able to have a release in the next week.
Do you want issue8133 to be a release blocker?
Pending the resolution of a few Mac OS issues (#8068, #8069, and
#8133), I'm not going to tag the release at the moment. Hopefully,
we'll still be able to have a release in the next week.
--
Regards,
Benjamin
___
Python-Dev mailing list
Python-Dev@pytho
Hi,
2010/2/15 Benjamin Peterson
> 2010/2/15 "Martin v. Löwis" :
> > Stefan Behnel wrote:
> >> Benjamin Peterson, 13.02.2010 03:52:
> >>> It's about time for another 3.1 bug fix release. I propose this
> schedule:
> >>>
> >>> March 6: Release Candidate (same day as 2.7a4)
> >>> March 20: 3.1.2 F
2010/2/15 "Martin v. Löwis" :
> Stefan Behnel wrote:
>> Benjamin Peterson, 13.02.2010 03:52:
>>> It's about time for another 3.1 bug fix release. I propose this schedule:
>>>
>>> March 6: Release Candidate (same day as 2.7a4)
>>> March 20: 3.1.2 Final release
>>
>> Does a crash like #7173 qualify
Stefan Behnel wrote:
> Benjamin Peterson, 13.02.2010 03:52:
>> It's about time for another 3.1 bug fix release. I propose this schedule:
>>
>> March 6: Release Candidate (same day as 2.7a4)
>> March 20: 3.1.2 Final release
>
> Does a crash like #7173 qualify as a blocker for 3.1.2?
I'm not the r
Benjamin Peterson, 13.02.2010 03:52:
> It's about time for another 3.1 bug fix release. I propose this schedule:
>
> March 6: Release Candidate (same day as 2.7a4)
> March 20: 3.1.2 Final release
Does a crash like #7173 qualify as a blocker for 3.1.2?
Stefan
___
Le Fri, 12 Feb 2010 20:52:23 -0600, Benjamin Peterson a écrit :
> It's about time for another 3.1 bug fix release. I propose this
> schedule:
>
> March 6: Release Candidate (same day as 2.7a4)
> March 20: 3.1.2 Final release
Looks perfect to me!
Antoine.
__
It's about time for another 3.1 bug fix release. I propose this schedule:
March 6: Release Candidate (same day as 2.7a4)
March 20: 3.1.2 Final release
--
Regards,
Benjamin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailm
On Jan 17, 2010, at 4:21 AM, Martin v. Löwis wrote:
> Barry was once proposing time-based releases; this idea didn't really
> catch on.
I'm still a proponent of this, but it doesn't seem like there's enough support
for it.
> It's the release manager who decides when the next bug fix release wil
In article <4b53135a.7060...@gmail.com>,
Nick Coghlan wrote:
> Antoine Pitrou wrote:
> > Ned Deily acm.org> writes:
> >> I've recently seen a couple of references to 3.1.2 go by in
> >> checkins which made me wonder whether dates have been proposed yet
> >> for updates to either 3.1 or 2.6. I d
Antoine Pitrou wrote:
> Ned Deily acm.org> writes:
>> I've recently seen a couple of references to 3.1.2 go by in
>> checkins which made me wonder whether dates have been proposed yet
>> for updates to either 3.1 or 2.6. I don't recall seeing any and I
>> didn't see any references in the PEPs. S
Ned Deily acm.org> writes:
>
> I've recently seen a couple of references to 3.1.2 go by in checkins
> which made me wonder whether dates have been proposed yet for updates to
> either 3.1 or 2.6. I don't recall seeing any and I didn't see any
> references in the PEPs. Some advance warning wo
Ned Deily wrote:
> I've recently seen a couple of references to 3.1.2 go by in checkins
> which made me wonder whether dates have been proposed yet for updates to
> either 3.1 or 2.6. I don't recall seeing any and I didn't see any
> references in the PEPs. Some advance warning would be nice.
Ned Deily wrote:
> I've recently seen a couple of references to 3.1.2 go by in checkins
> which made me wonder whether dates have been proposed yet for updates to
> either 3.1 or 2.6. I don't recall seeing any and I didn't see any
> references in the PEPs. Some advance warning would be nice.
I've recently seen a couple of references to 3.1.2 go by in checkins
which made me wonder whether dates have been proposed yet for updates to
either 3.1 or 2.6. I don't recall seeing any and I didn't see any
references in the PEPs. Some advance warning would be nice. I assume
that some criti
16 matches
Mail list logo
