2.1.0b5 or 2.1.0rc1?

[John Arbash Meinel]

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

According to our timeline:
  https://edge.launchpad.net/bzr/2.1

The release in January is meant to be 2.1.0rc1 with a two week
turnaround into 2.1.0rc2 and 2.1.0 final being at the beginning of
February. I'm pretty sure Martin put that schedule together so that
2.1.0 final will be well in advance of the code freeze for Lucid.

This sounds like a reasonable process to me, though it would mean that
we would have a fairly short 2.1.0b4 => 2.1.0rc1 cycle. (Which is mostly
my fault because I injected a 2.1.0b4 that Martin didn't originally have
planned.)

Since we'll also be having some holiday time in there this seems pretty
short, but not terrible. I was just updating NEWS, and was wondering if
I should put:

bzr 2.1.0rc1 (not released yet)
##############################

I don't think we want that in the bzrlib.version_info tuple until we
actually make the release (just like we do 2,1,0,'dev',4 until it
becomes 2,1,0,'beta',4).

Anyway, once 2.1.0rc1 comes out, I'm pretty sure the plan is to start
2.2.0b1 as the next 'dev' version.

Does this sound reasonable to everyone?

John
=:->

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

iEYEARECAAYFAksnMxYACgkQJdeBCYSNAAPvCQCfeI5DngSeU8otWkRL8Ow6QVD2
IbsAnRA5v8pIGYX0YPixFvgVn5OYVR2z
=rSQl
-----END PGP SIGNATURE-----