[ANN] bzr 2.4b3 has gone gold

[Gordon Tyler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
On 5/26/2011 7:28 PM, John Arbash Meinel wrote:
> On 05/26/2011 06:44 PM, vila wrote:
>> And yet another beta for the 2.4 series !
>
>> We had a very productive sprint last week and landed a lot, this
> should
>> make this beta an interesting one.
>
>> See the release notes for details and make your package and
>> installer builders rock !
>
>> I'll make the official announcement next Tuesday morning UTC
> (2011-05-31)
>> with... whatever packages/installers are available at this
>> point.
>
>> I know the windows packagers have been hard at work for the
>> 2.3.3
> one so
>> hopefully they'll be able to beat the OSX people for once ;)
>
>> The tarball has been uploaded at
>> https://launchpad.net/bzr/2.4/2.4b3
>
>> Have fun !
>
>> Vincent
>
>
> Of course, Vincent cheated by announcing this 2 hours after
> end-of-day time. Thinking he could give the Mac OSX guys a full
> day's head start on packaging. Good thing I checked my email in the
> evening to see the gauntlet thrown down, pick it up and respond to
> the challenge.

Curse you! *shakes fist* Still building... I saw the email earlier but
I don't have access to the Mac until I get home from work. :P

Uploading now, should be available in a few minutes.

> Running into that revealed the "buildout doesn't actually
> re-download newer branches" bugs. It will populate a branch with
> the right tag if you don't have anything, but if something is
> there, it won't re-download a branch. So we really just have to
> nuke build-win32/*/bzr-*/ between releases. And all we really save
> is re-downloading some of the Tortoise and SVN libs.

It would be nice to have a somewhat generic package dependency
resolution tool that knew how to download and unpack tarballs or
checkout bzr branches according to some version specification and
would automagically do The Right Thing (TM) when those version
specifications change compared to what is sitting in the filesystem.

On a related note, when fetching or updating a package from a bzr
branch, what would be faster: lightweight checkout + update or branch
+ pull?

Ciao,
Gordon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
iQEcBAEBAgAGBQJN3ugXAAoJEIrPJfWinA2uPtUH/RZ86K4cSs/sMQvFisyv9hS7
r7wY8fRjPO0ciCuJ4/5n3a5soAMSRYD/EoRgjiEAgX5TOqhWKaJ4saayj/nr3ZH8
POEX2GXFHFYcoGXajvidEjRYCZTxT9ne+jVqSRqeC0O9/0j97wZvR770sAf0l33U
WBVA79WnBnclIE4MRafh+hIkuCrAHZmpwNuo5LtgbrynICG8ucqJZ53I/97vleQp
PsGvYwMcrGYx6PZtc5tmIxdaK/sQP6SXDg17r08ofpCnBIChJrwtSDWXN/fCNRQz
BXYARc0UGTVj1a7cnV+9rZbYPxfSvljA08vKTkycKWRI/vdT2Zq1o3U1EjZWYEI=
=bysQ
-----END PGP SIGNATURE-----