-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been out of town since Friday, but I don't yet see anything in
the 700 billion email messages I'm now catching up on that leads me to
think we need to delay the release. Yay!
I will be on irc later today and will be trolling through the tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Over the next several hours I will be cutting Python 2.6. All lights
and buildbots are go for final release tonight.
I have not yet heard from Trent about press releases, so we'll have to
do those after the fact.
I am also planning on releasi
On Wed, Oct 1, 2008 at 12:36 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> Over the next several hours I will be cutting Python 2.6. All lights and
> buildbots are go for final release tonight.
>
> I have not yet heard from Trent about press releases, so we'll have to do
> those after the fact.
P
On Wed, Oct 1, 2008 at 3:33 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 1, 2008 at 12:36 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> The trunk and 3.0 branches are officially frozen until further notice. You
>> /must/ contact me on irc if you need to make any changes.
>
> Why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 4:33 PM, Guido van Rossum wrote:
On Wed, Oct 1, 2008 at 12:36 PM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
Over the next several hours I will be cutting Python 2.6. All
lights and
buildbots are go for final release tonight.
I
>> Press releases can lag behind, but I hope that this time the Windows
>> and OSX installers will be released together with the main tarball.
>
> I agree, but I have not heard from Ronald or Martin about that yet.
That's because you didn't ask, I guess.
> Ronald, are you still planning on buil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 5:00 PM, Martin v. Löwis wrote:
Press releases can lag behind, but I hope that this time the Windows
and OSX installers will be released together with the main tarball.
I agree, but I have not heard from Ronald or Martin about t
> Yes, I should have been more proactive in getting everyone coordinated,
> but as I say we've all known about today's release date for a very long
> time.
Sure. However, creating the tag around 22:00 UTC (or later) makes it
fairly difficult for me to create binaries on the same day. To have
binar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 5:19 PM, Martin v. Löwis wrote:
Yes, I should have been more proactive in getting everyone
coordinated,
but as I say we've all known about today's release date for a very
long
time.
Sure. However, creating the tag around 22:
> Yes, of course that makes sense. What would be a better time for you
> Martin? I would like to at least debug this aspect of the PEP so that
> next time we can coordinate better.
As I said: If you create the tag in your morning, I can do the binaries
before heading home. Please send an email m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 5:32 PM, Martin v. Löwis wrote:
Yes, of course that makes sense. What would be a better time for you
Martin? I would like to at least debug this aspect of the PEP so
that
next time we can coordinate better.
As I said: If yo
Martin v. Löwis wrote:
> Of course, Anthony is in a different time zone, so when he created
> the tag in his evening, I had all day, and the binaries would still
> be available when he got up the next morning.
That's a good point - if Barry is on the US west coast somewhere, it
actually works out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 5:44 PM, Nick Coghlan wrote:
Martin v. Löwis wrote:
Of course, Anthony is in a different time zone, so when he created
the tag in his evening, I had all day, and the binaries would still
be available when he got up the next morni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The 2.6 tag has been created.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOP1eHEjvBPtnXfVAQLDagP/RrRQrSCzLGBZK06kFR46p42rFv42ixnq
IRWgBWd5wRfFAivuMrkntTyTNMniH+ujTeSaJ6oplVY78RGGBmPzERI8xBhOsZj4
HYe/X51Vmjh8hTTYqs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Barry Warsaw wrote:
> IIUC, the critical bottleneck is tagging the tree, so the RM needs to
> make it far enough through the PEP to get to that point. Of course that
> does mean freezing the tree, and I don't think it's too difficult to do
> that.
I
If there's a screwup, and you need to recut the branch, you want to be
sure someone else hasn't been helpful and added something else to the
repo.
On Thu, Oct 2, 2008 at 9:37 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Barry Warsaw wrote:
>> IIUC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Although I'm not quite ready to thaw the tree and make the
announcement, the Python 2.6 final tarballs are now on dinsdale. If
you'd like to grab them and take a look, run the tests, etc, that
would be great.
@dinsdale[/data/ftp.python.org/pu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 7:01 PM, Barry Warsaw wrote:
Although I'm not quite ready to thaw the tree and make the
announcement, the Python 2.6 final tarballs are now on dinsdale. If
you'd like to grab them and take a look, run the tests, etc, that
wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 7:06 PM, Barry Warsaw wrote:
As reported on irc, the source tarballs are too huge because Doc/
build got included. Working on a fix now.
The new tarballs are up. I'm re-running the test with them.
- -Barry
-BEGIN PGP SIG
There should be a way to re-tag only the file(s) that contain the fix.
On Wed, Oct 1, 2008 at 4:00 PM, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> If there's a screwup, and you need to recut the branch, you want to be
> sure someone else hasn't been helpful and added something else to the
> repo.
Sure, but that's more fiddly. From experience, when you're cutting
releases, making things as simple as possible is a good thing.
On Thu, Oct 2, 2008 at 11:35 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> There should be a way to re-tag only the file(s) that contain the fix.
>
> On Wed, Oct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 9:47 PM, Anthony Baxter wrote:
Sure, but that's more fiddly. From experience, when you're cutting
releases, making things as simple as possible is a good thing.
Especially when a lot of the process is scripted.
- -Barry
-B
That's why I wrote the welease.py script. Dunno if you've been using
it. I wanted to make the release process as foolproof as possible so I
wouldn't screw it up :-)
On Thu, Oct 2, 2008 at 12:02 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Oc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 10:05 PM, Anthony Baxter wrote:
That's why I wrote the welease.py script. Dunno if you've been using
it. I wanted to make the release process as foolproof as possible so I
wouldn't screw it up :-)
Unfortunately, I had a lot of p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, I /think/ everything's done, except:
* write and send the announcement
* Martin to upload msi's tomorrow
* fix docs.python.org
Actually, I couldn't figure out what to do to make docs.python.org and
all the other current/dev docs symlinks do
> There should be a way to re-tag only the file(s) that contain the fix.
It's possible to edit the tag itself (rather than the trunk/maintenance
branch), but then you also need to merge the changes back into the
trunk. Also, editing the tag effectively makes it a branch; such usage
is discouraged
> You're absolutely right and that sounds good. I will update the PEP
> accordingly. Martin, Ronald, Sean, what timezones are you in? I am
> US/Eastern.
I'm in CET (Central European), that GMT+2 in DST, and GMT+1 otherwise.
As for Sean: Sean and me had agreed that we won't do RPMs anymore for
On Thu, Oct 2, 2008 at 4:08 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> You're absolutely right and that sounds good. I will update the PEP
>> accordingly. Martin, Ronald, Sean, what timezones are you in? I am
>> US/Eastern.
>
> I'm in CET (Central European), that GMT+2 in DST, and GMT+1
I propose that the release of 3.0rc2 is deferred until all release
blockers have been resolved (either by actually fixing them, or by
carefully considering that they shouldn't actually block the release).
What else is the point of having the "release blocker" priority, if
they don't actually manag
29 matches
Mail list logo
