On Apr 11, 2009, at 8:20 AM, Mark Dickinson wrote:
On Fri, Apr 10, 2009 at 2:31 PM, Barry Warsaw
wrote:
bugs.python.org is apparently down right now, but I set issue 5724 to
release blocker for 2.6.2. This is waiting for input from Mark
Dickinson,
and it relates to test_cmath failing on S
On Fri, Apr 10, 2009 at 2:31 PM, Barry Warsaw wrote:
> bugs.python.org is apparently down right now, but I set issue 5724 to
> release blocker for 2.6.2. This is waiting for input from Mark Dickinson,
> and it relates to test_cmath failing on Solaris 10.
I'd prefer to leave this alone for 2.6.2.
I wanted to cut Python 2.6.2 final tonight, but for family reasons I
won't be able to do so until Monday. Please be conservative in any
commits to the 2.6 branch between now and then.
bugs.python.org is apparently down right now, but I set issue 5724 to
release blocker for 2.6.2. This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to release Python 2.6.2 the week after the conference. I've
talked to a few people here about it and the general consensus is that
we do one brown-paper-bag-avoiding release candidate first. Looking
at the calendar, I propose the foll
Jason R. Coombs wrote:
> I'm still holding my breath for Python 2.6.2, which fixes a Windows
> DLL linking issue that was already fixed in 3.0.1. Obviously, the
> proposed schedule has passed, but I would prefer a release sooner
> than later.
I suggest you start breathing again.
Martin
_
I'm still holding my breath for Python 2.6.2, which fixes a Windows DLL linking
issue that was already fixed in 3.0.1. Obviously, the proposed schedule has
passed, but I would prefer a release sooner than later.
Of course, that's just my preference.
Regards,
Jason
> -BEGIN PGP SIGNED MESS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 18, 2009, at 1:49 AM, Brett Cannon wrote:
If there are really enough fixes to warrant it, sure. Otherwise
would it be
worth more to just wait until after PyCon where there is a bigger
chance of
fixed issues?
Good point.
Barry
-BEGI
On Tue, Feb 17, 2009 at 12:18, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thinking again about 3.0.2.
>
> If we'd like to do bug fix releases before Pycon, I suggest Monday March
> 9th for code freeze and tagging. That would mean a Tuesday March 10th
> release.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thinking again about 3.0.2.
If we'd like to do bug fix releases before Pycon, I suggest Monday
March 9th for code freeze and tagging. That would mean a Tuesday
March 10th release.
What do you think?
Barry
-BEGIN PGP SIGNATURE-
Version
