-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 8, 2008, at 7:04 AM, Paul Moore wrote:
2008/9/8 wesley chun <[EMAIL PROTECTED]>:
the goal is admirable, but unless there are paying sponsors that
require this deadline be met, i'd suggest that we can push the
releases until they're ready. t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 7, 2008, at 4:12 PM, Fredrik Lundh wrote:
Barry Warsaw wrote:
(I have a few minor ET fixes, and possibly a Unicode 5.1 patch,
but have had absolutely no time to spend on that. is the window
still open?)
There are 8 open release blockers
2008/9/8 wesley chun <[EMAIL PROTECTED]>:
> the goal is admirable, but unless there are paying sponsors that
> require this deadline be met, i'd suggest that we can push the
> releases until they're ready. the changes that 2.6 and 3.0 bring are
> too major to be released before they are ready for
>> Barry Warsaw wrote:
>>> I'm not going to release rc1 tonight.
>>> I'd like to try again on Friday and stick to rc2 on the 17th.
>
> There are 8 open release blockers, a few of which have patches that need
> review. So I think we are still not ready to release rc1. But it worries
> me because I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 7, 2008, at 10:51 AM, Fredrik Lundh wrote:
Barry Warsaw wrote:
I'm not going to release rc1 tonight. There are too many open
release blockers that I don't want to defer, and I'd like the
buildbots to churn through the bsddb removal on a
On Wed, Sep 3, 2008 at 8:41 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm not going to release rc1 tonight. There are too many open release
> blockers that I don't want to defer, and I'd like the buildbots to churn
> through the bsddb removal
On Wed, Sep 3, 2008 at 8:41 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm not going to release rc1 tonight. There are too many open release
> blockers that I don't want to defer, and I'd like the buildbots to churn
> through the bsddb removal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 7:31 AM, Facundo Batista wrote:
(I'll be hanging around in #python-dev today and tomorrow, btw, ping
me if I can help you)
Me too, though I'm a bit busy at work. Ping my nick 'barry' if you
need any RM-level decision.
- -Ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 3:28 AM, Mark Hammond wrote:
Barry writes:
In addition, Mark reported in IRC that there are some regressions in
the logging module.
3772 logging module fails with non-ascii data
Which according to the IRC discussion doesn't a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 12:14 AM, Raymond Hettinger wrote:
[Barry]
I'm not going to release rc1 tonight.
Can I go ahead with some bug fixes and doc improvements
or should I wait until after Friday?
Doc fixes are fine. Please have bug fix patches re
2008/9/4 Raymond Hettinger <[EMAIL PROTECTED]>:
> Can I go ahead with some bug fixes and doc improvements
> or should I wait until after Friday?
Doc improvements: go ahead.
Bug fixes: the patchs should be revised by other developer.
(I'll be hanging around in #python-dev today and tomorrow, btw
Barry writes:
> In addition, Mark reported in IRC that there are some regressions in
> the logging module.
3772 logging module fails with non-ascii data
Which according to the IRC discussion doesn't apply to py3k. The fix for
2.6 is quite trivial...
Cheers,
Mark
_
[Barry]
I'm not going to release rc1 tonight.
Can I go ahead with some bug fixes and doc improvements
or should I wait until after Friday?
Raymond
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-30
13 matches
Mail list logo
