bzr 2.1 timeline

[John Arbash Meinel]

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

Martin Pool wrote:
> 2.0 is now branched, frozen, and on the verge of release.  We're going
> to keep supporting that branch with bug fixes for the next several
> months at least.  In the mean time, the work on trunk is going to end
> up in a 2.1 early next year.  (See
> <http://doc.bazaar-vcs.org/developers/cycle.html> for background.)
> 
...

> Therefore:
> 
> 1 Oct   2.1b1
> 1 Nov   2.1b2
> 1 Dec   2.1b3
> 1 Jan   2.1rc1 --- and 2.1 branches off into a bugfix-only branch,
> leaving trunk open for new features towards 2.2
> 1 Feb   2.1.0
> 
> Check my sums?  Are there other deadlines we should take into account?
> 
> I'd like to slightly tweak the policy so that for a clearer
> distinction from the series, we call the major releases 2.0.0 or
> 2.1.0, rather than squashing the final 0.
> 
> So that gives 5 months of open development (with a couple of weeks
> already passed.)
> 

So I believe you mentioned creating all of these milestones in another
email, but I didn't find it, so I'm responding here.

My recent changes to "not squash the final 0" mean that bzr itself will
report as "bzr 2.1.0dev", etc. And that means that I updated all of the
releases accordingly. So it is now:

1 Oct 2.1.0b1
1 Nov 2.1.0b2
1 Dec 2.1.0b3
1 Jan 2.1.0rc1
1 Feb 2.1.0    # Though I thought the plan was to have rc1 => final be 1
               # week and not 1 month.

I've played with it different ways, but I think in the end the
consistency of seeing that 2.1.0b1 comes before 2.1.0 is nice.

I also went back and updated 2.0.0rc2 and 2.0.0 since those will also be
effected.

John
=:->

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

iEYEARECAAYFAkqyXp4ACgkQJdeBCYSNAAOMngCgjxLWWi3rz359/dmMrwrzn4o1
wfwAn1MtgyFG13OmEauyjDnfR56x9GD/
=qRWH
-----END PGP SIGNATURE-----