Friends, please let us remind now that we proposed the code freeze for OpenSSL 0.9.3 for today (see STATUS document) in order to be able to kick out the release next week (Monday, May 17th). When you've large or compatibility-problematic changes in your queue, either decide to queue them for later consideration or finally commit them now for 0.9.3. At least today should be the last day where features or similar changes are comitted to the repository. Then until the release only bugfixes, cleanups and documentation should be comitted. We've done lots of changes since 0.9.2b and so a dedicated testing week is more than reasonable. Please try to not break anything in the last minute. I've again enabled the snapshot tarball rolling to occur every 6 hours. The tarballs can be (as usual) found under ftp://ftp.openssl.org/snapshot/. Every OpenSSL user who wants to participate in the release procedure is now encauraged to grab the snapshots (at least once) this week and try it out on as much platforms as possible. Success and problem reports should be posted to [EMAIL PROTECTED] - as usual. Last time I've played the release manager. This time some other core team member should overtake this important task, please. I propose that Ben or Steve this time volunteer for this job. To avoid confusion (especially because we've new developers who are perhaps not familiar with it), the task of the release manager is: 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? Greetings, Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com PS, I've already ported Apache/mod_ssl to the latest OpenSSL state and stress tested it on the weekend on my FreeBSD 3.1 box. All worked fine for my tests, so I think this at least is a first indication that we've not broken too much existing applications by our API changes (puhhhh!). It was a little bit nasty to have to convert all "STACK" and "const" related things, but for the average application it's acceptable and the stuff initially looked more fatal than it actually was.... ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
