bzr 1.8 release plans

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> A quick update on bzr 1.8 releases:
> 
> bzr 1.8rc1 came out last Tuesday.  I'm trying to get the Windows
> packages built on a Windows virtual server, and am having some trouble
> getting distutils to properly work with the x64 compiler.
> 
> (I have a copy of Visual Studio Express, and the Windows SDK, which
> together should provide an x64 compiler.  However, the vcvarsall.bat
> script called by distutils just can't seem to find it.)

What version of VSE? The problem is that distutils only likes to build
with the identical copy of the compiler. So generally it wants you to
use Visual Studio 2003. And IIRC, it isn't available from Microsoft
anymore. (There are a couple 3rd-party sources that you can find with a
google search.)

I'm also a little concerned about a 64bit platform, but mostly as just
another variable that we have to look out for.

Anyway, I've just always installed gcc-mingw32 which python already
knows how to use. (You just need to pass -c mingw32 to 'build_ext', or
configure your distutils by creating a config file in
Python25/site-packages.)

> 
> There is a copy of bzr in the PPA, but currently no bzrtools, even
> though there is a 1.8.0 upstream release.  As far as I can see
> bzrtools has not yet been updated to use the builddeb system used for
> bzr.

There is a branch that Jelmer has for packaging bzrtools for debian,
which works just fine for packaging bzrtools for gutsy/hardy/intrepid (I
don't think it is correct for dapper.) Which is what I've been using.

There are branches for:
lp:~bzr/bzrtools/packaging-dapper

etc,

Though I've been doing it as an all-in-one package:
lp:~bzr/bzrtools/ppa

Basically, I use the same basic process, but I do it all in the same
branch. I merge Jelmer's build branch into this, fixing changelog. Then
I update the changelog for gutsy, commit, build. Update for hardy,
commit, build, etc.

> 
> I'm planning to do 1.8 final tomorrow, at least as a source release
> and into the PPA, and then get Windows installers working.
> 

So... The proper standalone installer can only be properly built by Mark
Hammond at this point. I can certainly issue a "make installer" on this
machine, but I don't know the exact configuration he has. Because he
puts bzr-svn, tbzr, qbzr all in the right locations and at the right
versions.


I did go ahead and do the one-line fix to "from bzrlib import osutils"
just to get 1.8rc1 python-based installers built, and I've uploaded
them. They *do* include the compiled extensions, since I'm using mingw32
rather than msvc at this point.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjzZnMACgkQJdeBCYSNAAOn3gCggeCTmQLUsGI6Lk31DHN3ZHwg
ecIAn3u1AFAZcpjRe5Dm/cWGw9gp2sLA
=HKxY
-----END PGP SIGNATURE-----