getting 2.0.0 finished, packaged, and into Karmic

[Martin Pool]

The 2.0.0 code has been frozen for about a week now and testing seems
to have found no problems that would block us making a final release,
which is great.  There are a few non-code things we need to do:

 * Get 2.0.0 or 2.0.0rc2 into Karmic, which requires asking for a
feature freeze exception to upgrade from 1.18, and requires all the
plugins shipped in Ubuntu be up to date.
   + Confirm all plugins can be updated
   + Ideally, have packages representing the state we want to reach in
our own PPA
   + File for an FFE
   + Actually get the packages uploaded

 * Finish and set up the web site.  It would be very nice and make a
lot of sense to do this before we announce 2.0 rather than afterwards.
   + Agree on any further changes to the site
   + Agree on text
   + Get ready to migrate: url redirections etc
   + Cross-browser or any other testing?
   + Get it uploaded onto the actual site

 * See what plugins need either code updates or new releases for 2.0.
Jelmer mentioned updating bzr-hg/git/svn this week.

 * Check that 2.0.0 can be packaged on all platforms.  There has been
some feedback and activity on the Windows installers, and they're now
present for 2.0rc2, but there is no Mac installer there yet.  There
are mac dmgs for 1.18, and the changes to 2.0 are not too likely to
have broken anything.   (See <https://launchpad.net/bzr/+download>)

Anything else?

I'm going to look into filing for a feature freeze exception, and also
checking the state of the packages currently in the bzr-beta-ppa.

-- 
Martin <http://launchpad.net/~mbp/>