Bazaar 2.1.0b3 what to do?

[John Arbash Meinel]

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

So thanks to Martin we have discovered a "Critical" regression for
Bazaar 2.1.0b2, namely the new proxy code is incompatible with python
2.4. Vincent has a fix for it, which I'm trying to land into at least
bzr.dev, though I'm running into problems with codehosting right now.

Anyway, once that lands into bzr.dev, we have a question to answer.
Namely, how do we want to do bzr 2.1.0b3. We settled on a policy that we
won't do RC's for the beta releases, instead we'll just release the next
one early if there is a regression.

Which is fine, but the questions I have are:

1) Are there any other regressions that we should target for 2.1.0b3? I
   don't really want to release 2.1.0b4 the next week.

2) Should we include all changes since 2.1.0b2 that have landed in
   bzr.dev in the 2.1.0b3 release? Or should we cut a specific new
   branch directly from 2.1.0b2 and just include this fix?

3) What to do about the 2.1.0b2 announcement? I still haven't given a
   public announcement because I still can't build the windows
   installers. (I'm stuck waiting for the pre-compiled chm files to be
   built, and that seems to be stalled w/ Ian not feeling well, and
   Martin trying to take over the doc building.)

   On the plus side, while waiting for that to sort out, I think I've
   almost got the EC2 host ready for doing the builds, rather than using
   Kerguelen. It isn't finalized because we still need to sort out
   building with VS 2008 (either installing the full version, or
   figuring out how to build tbzr w/ Express edition.)

   I would be okay just skipping 2.1.0b2 as a public release, and only
   announcing 2.1.0b3 when it is ready. It would just be the first time
   we've ever done that, so I figured I should check first.

4) When? I'm thinking early next week, which would mean sorting through
   some of this at the sprint. Which in some ways is good, though
   possibly not a great use of sprinting time.

Anything else?

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

iEYEARECAAYFAkrzIZEACgkQJdeBCYSNAAO+NgCfWQnqpe+QWrP+BtefMYzNQp3d
Q8UAn0j1wOM7+AljEa46+9UwYrw2WVKJ
=efGc
-----END PGP SIGNATURE-----