Barry Warsaw wrote:
>>> Okay, let's go ahead and make it official.
>>> I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern
>>> (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to
>>> that: 2200 UTC Friday 29-Feb-2008.
>>
>> Argh! I was going to check the last of th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 28, 2008, at 5:07 PM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
>> I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern
>> (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to
>> that: 2200 UTC Friday 29-Feb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 28, 2008, at 4:03 PM, Eric Smith wrote:
> Barry Warsaw wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>> On Feb 28, 2008, at 2:49 PM, Christian Heimes wrote:
>>> Hey Barry!
>> Hi Christian!
>>> When are you planing to freeze the cod
Barry Warsaw writes:
> I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern
> (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to
> that: 2200 UTC Friday 29-Feb-2008.
Is that enough time for the buildbots to do their thing and for you to
look at the page?
Alter
Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Feb 28, 2008, at 2:49 PM, Christian Heimes wrote:
>
>> Hey Barry!
>
> Hi Christian!
>
>> When are you planing to freeze the code of the trunk and branches/py3k
>> for the upcoming alpha releases? I'll merge the last mo
Barry Warsaw wrote:
> Okay, let's go ahead and make it official.
>
> I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern
> (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to
> that: 2200 UTC Friday 29-Feb-2008.
Linux is looking good. I've fixed some minor Windows iss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 28, 2008, at 3:03 PM, Chris Mellon wrote:
> On Thu, Feb 28, 2008 at 1:49 PM, Christian Heimes <[EMAIL PROTECTED]>
> wrote:
>> Hey Barry!
>>
>> When are you planing to freeze the code of the trunk and branches/
>> py3k
>> for the upcoming alp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 28, 2008, at 2:49 PM, Christian Heimes wrote:
> Hey Barry!
Hi Christian!
> When are you planing to freeze the code of the trunk and branches/py3k
> for the upcoming alpha releases? I'll merge the last modifications
> from
> 2.6 to 3.0 in a
On Thu, Feb 28, 2008 at 1:49 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Hey Barry!
>
> When are you planing to freeze the code of the trunk and branches/py3k
> for the upcoming alpha releases? I'll merge the last modifications from
> 2.6 to 3.0 in a couple of minutes. All tests on Linux a
Hey Barry!
When are you planing to freeze the code of the trunk and branches/py3k
for the upcoming alpha releases? I'll merge the last modifications from
2.6 to 3.0 in a couple of minutes. All tests on Linux are looking good,
except for the two profile tests on 3.0. I'm going to test Windows later
> (unless a complete working solution is presented in that other technology,
> and as long as that other technology still creates MSI files with
> free-as-in-beer tools).
Just out of interest, what's the reason for enforcing that the installer must
be an MSI? Or, rather, if I were to present an
11 matches
Mail list logo
