|
|||||||||||
|
[Design] 2.00 release plans
From: Hugh Daniel <hugh(at)road.toad.com>
Date: Tue Feb 18 2003 - 22:02:46 EST
Feb. 20 Feb. 20th, We cut an 2.00-rc1, it _will_ have warts that have to be fixed in following releases, so we get to suffer from .0 release disease just like every one else. Tough, we 'freeze' Thursday. The freeze conditions are that doc is NOT frozen and that everything else is, WARTS and all unless we find a 'failure' class bug. So there are two days to get in what needs to be, and it dam well better be minor. Note that if you have a patch or a dream that needs some structure to be different in the 2.00 series, time's up. Maybe if it's small enough we can accommodate you, maybe, and remember that 3.00 is not far off (2.00 is ment to be just a 'delivery' and not a 'development' platform). As project lead MCR is working on a list of things that will be changed before the freeze, there are a few known at this point. We will try to produce a -pre8 tonight (look for it on the FTP server) that is obviously very very close to what -rc1 will be. Feb. 28 Two big things happen February 28th. We intend to put out a 2.00 (final) that should be perfectly usable, but will have known warts. To deal with the warts and the like we will add a "Weather Report" as has been discussed before to the www.freeswan.org web page, this will give folks a paragraph description of the known state of current releases. Do note that these 'Weather Reports' will mostly _lag_ the release more then precede it. The other thing that happens on that Friday is that the daily snapshot on that Friday should have the first version of "co-terminal" SA's, thus a machine can have both WAVEsec _&_ OE running at the same time. This is only a first pass, we will see from that what needs do be done to make it working and polished. Mar. 07 We intend to release 2.01-pre1, with a target of a working co-terminal setup and every wart needed for FreeS/WAN use at IETF and beyond fixed. After this work will stop for about two weeks for a DNSsec workshop and IETF, after that we will consider a schedule for 2.01, likely in the second half of April. Please remember that our small team can't do everything everyone wants, not even what _we_ want to get done. This is a big and complex problem space and we are serious trying to do what no one else seems even willing to contemplate, make most machines secure most of the time. Thus if there is something that you would like have have working in FreeS/WAN, please at least test that something in the next 9 days. ||ugh Daniel hugh@freeswan.org Systems Testing & Project mis-Management The Linux FreeS/WAN Project http://www.freeswan.org Version: 2.6.3ia Charset: noconv Comment: For the matching public key, finger the Reply-To: address.
iQCVAwUBPlLz01ZpdJR7FBQRAQFygAQArn+MV18uoYxnAvlZ8MODUlwUEXlm3WLG
Pz1EKi7tDfYOLoFDwMz34YvNBroyx/is7fc1FTxM6sOm4bq8GEgUkW83d4LGUxTa
MvtroaLHwRagpiDBZIO+OTx0BmIqKPNxNUuLI0TcApHT/FWb35OP1vDMkf/cG4oj
salN8Xio6Y8=
Design mailing list Design@lists.freeswan.org http://lists.freeswan.org/mailman/listinfo/design Received on Wed Feb 19 20:09:01 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 12:59:32 EDT |
||||||||||
|
|||||||||||