Ralf S. Engelschall wrote:
> 1. to keep track of the problem reports and success reports in STATUS over
> the next week so no important problem is lost and the group gets an
> impression of the success and failure status of our baby.
> 2. to delegate problems to developers in order to get them fixed.
> (it's not the task primary task of the release manager to fix problems
> himself when not easily or immediately possible, of course!)
> 3. to make sure no developer commits any risky changes or only after
> approval with the release manager.
> 4. to finally roll the tarball next Monday on dev.openssl.org.
> 5. to move the tarball to the FTP and Web site and update
> all links, references, documentations, etc.
> 6. to send announcements to mailings lists and newsgroups.
>
> Ben? Steve? Can one of you overtake this important job for the group?
I guess I can do that, but I may have to delegate some of this
(particularly point 5, since I haven't paid much attention to the
website).
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
