Release Manager needed for 2.0

[Martin Pool]

Jono has done great work on recent releases, but now wants to hand
over the RM to someone else for the next release.  This should be our
2.0 release where the 2a format becomes the default.

The main jobs of the RM are to

 * remind people that the release is going to happen, and that they
have to land their changes
 * make the final decision about what should or shouldn't go in
 * actually cut the release, following the instructions in the developer docs

It specifically doesn't include making binary packages, and in general
we should be pushing towards making the RM process low latency.

I'm willing to do this myself but if someone else is keen speak now.

RM is a great opportunity for people to help with Bazaar development,
but I think for this release in particular we should go with someone
fairly experienced.

The regular dates to do this, getting back on Thursday releases, would
be: 2.0rc1 Thursday 6 August, 2.0final Thursday 13 August.

However, I think we should will leave open the option to either do a
longer rc period or to call this release 1.18 if it turns out that we
need further stabilization.  (Deprecations etc merged during this
cycle should be marked 1.18 for the sake of sorting.)

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