From: Joerg Walter (jhr.walter_at_[hidden])
Date: 2003-08-07 13:10:26
----- Original Message -----
From: "Beman Dawes" <bdawes_at_[hidden]>
To: "Boost Mailing List" <boost_at_[hidden]>
Sent: Thursday, August 07, 2003 5:43 PM
Subject: [boost] Release Manager's Checklist added
> I've added a detailed Release Manager's Checklist
> It will take up to 24 hours for this to be reflected on SourceForge's
> public CVS (although it is available right away for those with write
> There are five items on the checklist that take up the bulk of the release
> manager's time (see abbreviated descriptions below). The release manager
> near exhaustion by the time these are complete. I think we need to figure
> out a way to delegate this management effort to more people. (There are
> already quite a number of people helping with bits and pieces of the
> overall process, but we need to formalize that a bit more, IMO, so the
> release manager doesn't get lost in the details.)
> * Monitor inspection report to verify problems are being dealt with.
Unsure about that. I remember some mails from a wizard ;-)
> * Monitor regression tests to verify that errors are dealt with.
Unsure about that. ublas has some test failures (for ICC on windows for
example) which nobody is going to fix probably. OTOH this is the only
verification if cvs is consistent.
> * Monitor mailing lists to verify that patches are being dealt with.
Doesn't sf have a tracker for patches?
> * Monitor mailing lists and bug tracker to verify that bug reports are
> being dealt with.
Doesn't sf have a tracker for bugs?
> * Monitor CVS commits to verify content gets committed as planned.
Yep, seems like this one is a problem. Prereleases?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk