Barry Warsaw wrote:
On May 8, 2008, at 3:03 PM, Georg Brandl wrote:
While I'm +0 on the commit hook, it would help if a mail that announces
a freeze would
- not be hidden in a thread on python-dev and
- have a easily recognizable title, like "[TRUNK FREEZE] ".
I will make the freeze annou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 3:03 PM, Georg Brandl wrote:
While I'm +0 on the commit hook, it would help if a mail that
announces
a freeze would
- not be hidden in a thread on python-dev and
- have a easily recognizable title, like "[TRUNK FREEZE] ".
Michael Urman writes:
> I know this way is fairly entrenched in the python release process,
> but it sounds like it's using the tools incorrectly. In particular
> with subversion is very easy (compared to cvs) to branch and to switch
> branches locally. Why not create a new prerelease branch a
Terry Reedy schrieb:
Given that we cannot depend on timely mail/news propagation or on exact
day-ahead scheduling of a freeze, a current freeze notice either from the
repository or on a .../dev/status page might work better.
Nobody is going to look at such a page before making a commit :)
Ge
Given that we cannot depend on timely mail/news propagation or on exact
day-ahead scheduling of a freeze, a current freeze notice either from the
repository or on a .../dev/status page might work better.
___
Python-3000 mailing list
Python-3000@pyth
Barry Warsaw schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 8:21 AM, Christian Heimes wrote:
Barry Warsaw schrieb:
This is exactly what I'm thinking about!
-1
A technical solution never solves a social problem. It's just going to
cause more social and technical p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 9:41 AM, Michael Urman wrote:
On Thu, May 8, 2008 at 8:20 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
Or aggressively back out any changes from freeze time to tag time.
If we
don't add the commit hook lock, I will be very stric
On Thu, May 8, 2008 at 8:20 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> Or aggressively back out any changes from freeze time to tag time. If we
> don't add the commit hook lock, I will be very strict about this come the
> betas.
I know this way is fairly entrenched in the python release proces
Christian Heimes wrote:
Barry Warsaw schrieb:
This is exactly what I'm thinking about!
-1
A technical solution never solves a social problem. It's just going to
cause more social and technical problems.
All community members with svn write privileges must subscribe to the
Python developer li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 8:21 AM, Christian Heimes wrote:
Barry Warsaw schrieb:
This is exactly what I'm thinking about!
-1
A technical solution never solves a social problem. It's just going to
cause more social and technical problems.
In this case
Barry Warsaw schrieb:
> This is exactly what I'm thinking about!
-1
A technical solution never solves a social problem. It's just going to
cause more social and technical problems.
All community members with svn write privileges must subscribe to the
Python developer list. Committers must check
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 8, 2008, at 12:35 AM, raymond.hettinger wrote:
Author: raymond.hettinger
Date: Thu May 8 06:35:20 2008
New Revision: 62848
Log:
Frozensets do not benefit from autoconversion.
Since the trunk buildbots appear to be mostly happy (well those
12 matches
Mail list logo
