-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Adam wrote:
> If I am not completely wrong, this had been decided as well > as follows: A release will reach EOL when the next release > goes into maintenance mode, i.e. when the second next release > comes out. With the aimed release cycle of 6 months, this means > that each release will go into maintenance mode after 6 months > and reach EOL anonther 6 months later. Example: 3.2 will go into > maintenance mode in december 2008, when 3.3sdcheduled for > release, and 3.2 will reach EOL around June 2009 (?) when 3.4 is > scheduled. > > At least that is what Karolin had proposed and as far as I > remember at least noone had objected. (Time will tell if the > workload is manageable with such a tight release cycle.) Thanks. I couldn't remember if the maintenance release window had been decided. cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI/ycXIR7qMdg1EfYRAk1rAKDfxnOBQ7DSslc45gw6afCswf+0JACg50EH O03EupUOz1yHNw2l5jGECrw= =XU3u -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba