Re: [Samba] Samba 3.2, Samba 3.3 release planning
Original message Date: Wed, 22 Oct 2008 10:12:45 -0700 From: Jeremy Allison [EMAIL PROTECTED] Subject: Re: [Samba] Samba 3.2, Samba 3.3 release planning To: Christian Perrier [EMAIL PROTECTED] Cc: samba@lists.samba.org,[EMAIL PROTECTED] On Wed, Oct 22, 2008 at 06:35:50PM +0200, Christian Perrier wrote: Quoting Michael Adam ([EMAIL PROTECTED]): 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.3 is scheduled 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.) have you folks settled on a security support maintenance window, i.e. having some kind of commitment to try supporting security patches for releases that are no longer in maintenance mode. You see where I'm going, I think: what will happen if security issues are discovered after June 2009 ? Is there a chance that, at least in a best effort mode, some patches are provided for 3.2.* series? Yes, I think it's reasonable to provide security patches for a year after release, and I'll commit (personally) to doing that. Thanks Jeremy. And, of course, thanks to Karolin, Jerry and the rest of the Samba team. I think I will attempt a parallel 3.2, 3.3 release for those who are not ready to make a jump right away to a new relase. Many thanks too all! Cheers, Bill Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2, Samba 3.3 release planning
Hi William, Jerry, Gerald (Jerry) Carter wrote: William Jojo wrote: I love that releases are moving very quickly now. My only concern is keeping up with and determining what is appropriate as I continue to maintain AIX binaries on my web page. Presently I have already dropped the 3.0 series and have 3.2.4 available with the clustering option for AIX 5.3 and 6.1. I am trying to determine how best to support a 3.2 and 3.3 parallel set or if I should just drop 3.2 after 3.3.1 is released or some other arbitrary schedule. :-) :-) How long after 3.3 is released to production does the Samba team anticipate supporting the 3.2 line? That has not bee decided yet. The 3.0.x releases are in maintenance mode (transitioned as soon as 3.2.0 was released). The 3.0.x series will reach EOL on Jul 1, 2009. I expect that 3.2.x will be moved to maintenance mode as soon as 3.3.0 is released. Yes that had been decided exactly like this. maintenance == only critical bug fixes and security issues What we've not stated is how long it would be until v3.2.x reaches EOL. Based on past data, I expect 6 - 12 months, but that is just a guess and not really up to me. 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.3 is scheduled 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.) Please correct me if I am mistaken. If I were packaging Samba, I would only focus on the latest production release. Exactly. Of course it makes sense to try and package the pre-releases of the next release to see in time whether packaging will require adaptions. The pre-release phase is supposed to start roughly half way through the 6 months period. Cheers - Michael -- Michael Adam [EMAIL PROTECTED] SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.SerNet.DE, mailto: Info @ SerNet.DE pgpZj5i7lA6C8.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2, Samba 3.3 release planning
-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
Re: [Samba] Samba 3.2, Samba 3.3 release planning
Quoting Michael Adam ([EMAIL PROTECTED]): 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.3 is scheduled 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.) have you folks settled on a security support maintenance window, i.e. having some kind of commitment to try supporting security patches for releases that are no longer in maintenance mode. You see where I'm going, I think: what will happen if security issues are discovered after June 2009 ? Is there a chance that, at least in a best effort mode, some patches are provided for 3.2.* series? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2, Samba 3.3 release planning
On Wed, Oct 22, 2008 at 06:35:50PM +0200, Christian Perrier wrote: Quoting Michael Adam ([EMAIL PROTECTED]): 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.3 is scheduled 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.) have you folks settled on a security support maintenance window, i.e. having some kind of commitment to try supporting security patches for releases that are no longer in maintenance mode. You see where I'm going, I think: what will happen if security issues are discovered after June 2009 ? Is there a chance that, at least in a best effort mode, some patches are provided for 3.2.* series? Yes, I think it's reasonable to provide security patches for a year after release, and I'll commit (personally) to doing that. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2, Samba 3.3 release planning
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Ladanyi wrote: Is samba 3.2 development stopped and all concentration given to Samba 3.3 ? Because there isnt any further release note available for 3.2, but instead there are some notes for 3.3 ? Any future Samba 3.2.x release will be bug fix releases only. New develeopment is on-going in the 3.3 branch which is due for release mid-december. cheers, jerry - -- = Samba--- http://www.samba.org Likewise Software - http://www.likewisesoftware.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI/iN2IR7qMdg1EfYRAinOAJ9XqGIi8selGvRTrPAfTumNJxTupwCgwn1K +6VSHinH8qJkRl9/FnlxURA= =+eBo -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2, Samba 3.3 release planning
Original message Date: Tue, 21 Oct 2008 13:46:14 -0500 From: Gerald (Jerry) Carter [EMAIL PROTECTED] Subject: Re: [Samba] Samba 3.2, Samba 3.3 release planning To: Andreas Ladanyi [EMAIL PROTECTED] Cc: samba@lists.samba.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Ladanyi wrote: Is samba 3.2 development stopped and all concentration given to Samba 3.3 ? Because there isnt any further release note available for 3.2, but instead there are some notes for 3.3 ? Any future Samba 3.2.x release will be bug fix releases only. New develeopment is on-going in the 3.3 branch which is due for release mid-december. I love that releases are moving very quickly now. My only concern is keeping up with and determining what is appropriate as I continue to maintain AIX binaries on my web page. Presently I have already dropped the 3.0 series and have 3.2.4 available with the clustering option for AIX 5.3 and 6.1. I am trying to determine how best to support a 3.2 and 3.3 parallel set or if I should just drop 3.2 after 3.3.1 is released or some other arbitrary schedule. :-) :-) How long after 3.3 is released to production does the Samba team anticipate supporting the 3.2 line? Much appreciation and thanks to all on the Team! Cheers, Bill cheers, jerry - -- = Samba--- http://www.samba.org Likewise Software - http://www.likewisesoftware.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI/iN2IR7qMdg1EfYRAinOAJ9XqGIi8selGvRTrPAfTumNJxTupwCgwn1K +6VSHinH8qJkRl9/FnlxURA= =+eBo -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2, Samba 3.3 release planning
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 William Jojo wrote: I love that releases are moving very quickly now. My only concern is keeping up with and determining what is appropriate as I continue to maintain AIX binaries on my web page. Presently I have already dropped the 3.0 series and have 3.2.4 available with the clustering option for AIX 5.3 and 6.1. I am trying to determine how best to support a 3.2 and 3.3 parallel set or if I should just drop 3.2 after 3.3.1 is released or some other arbitrary schedule. :-) :-) How long after 3.3 is released to production does the Samba team anticipate supporting the 3.2 line? That has not bee decided yet. The 3.0.x releases are in maintenance mode (transitioned as soon as 3.2.0 was released). The 3.0.x series will reach EOL on Jul 1, 2009. I expect that 3.2.x will be moved to maintenance mode as soon as 3.3.0 is released. maintenance == only critical bug fixes and security issues What we've not stated is how long it would be until v3.2.x reaches EOL. Based on past data, I expect 6 - 12 months, but that is just a guess and not really up to me. If I were packaging Samba, I would only focus on the latest production release. cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI/laiIR7qMdg1EfYRAmcbAJ4pcc9a2mJvpMhvB29WapolX6YH9wCgtu6y TXcKxtS7V/Gt+G0Vo1LUhy0= =nkM3 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
