bzr 1.13 release manager wanted

[James Westby]

On Tue, 2009-03-10 at 14:24 -0500, Bob Tanner wrote:
> On 2009-02-17 21:47:12 -0600, Bob Tanner <tanner at real-time.com> said:
> 
> > I will volunteer.
> > 
> > I read http://doc.bazaar-vcs.org/latest/developers/releasing.html
> 
> Trying to understand the release process more.
> 
> james_w from irc pushed the 1.13rc1 into PQM, I understand I cannot do 
> that because PQM does not know my key. What I would like to know, so I 
> can add the details to the Releaseing document.
> 
> - How does one get their key into PQM? Couple emails with mbp tells me 
> it's a manual process. Correct?

Yes, it is. PQM access is usually restricted to those who have submitted
some patches and done some reviews, but Martin may wish to change the
rules for release managers who haven't reached this point yet.

> - How does one push releases to PQM? Step 8 of the Releasing document 
> say 'bzr push', but if this is your first time you need a place to push 
> it too.

The "pqm-submit" line immediately afterwards is what tells PQM to merge
the changes, the "push" just makes them available in a public branch 
that it can merge from. HACKING.txt explains how to set up your system
to make this work. A pointer to that might be a good idea.

> - When a release is pushed to PQM, do you get a notification? via 
> email? Step 9 says when PQM succeeds pull down the master release 
> branch. I'd like to know when it succeeds and how I'll know.

Yeah, there is an email sent to the submitter. You can also watch
http://pqm.bazaar-vcs.org/ to see the progress.

Thanks,

James