Re: Timescale for 8.0.x EOL
On Tue, Jun 6, 2017 at 3:24 PM, Felix Schumacherwrote: > > > Am 6. Juni 2017 20:39:44 MESZ schrieb Violeta Georgieva > : >>Hi, >> >>2017-06-05 16:51 GMT+03:00 Mark Thomas : >>> >>> On 19/05/17 23:19, Christopher Schultz wrote: >>> >>> >>> >>> > My proposal, adapted from the thread before discussion ceased last >>summer: >>> > >>> > 1. Set Tomcat 8.0.x EOL date for 31 May 2018 >>> > 2. Discontinue monthly release cadence for Tomcat 8.0.x after >>8.0.45 >>> > 3. Make these announcements as soon as we have agreed to the >>details for >>> > #1 and #2 >>> >>> Yet again I managed to respond to the sender rather than the list... >>> >>> +1, for #1 and #3 assuming that we make this 30 June 2018. >>> >>> I'm neutral on #2 since it is unlikely to be me doing the releases. >>I've >>> no objection to monthly releases if someone wants to take that on. I >>> suspect every 2 to 3 months would be sufficient. >> >>In case there are enough people that can test the releases and vote I >>can >>do the releases for example every 2 months. > > I will try to test and vote. +1, me too :) > > Felix > >> >>Regards, >>Violeta >> >>> >>> Mark >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: dev-h...@tomcat.apache.org >>> > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
Am 6. Juni 2017 20:39:44 MESZ schrieb Violeta Georgieva: >Hi, > >2017-06-05 16:51 GMT+03:00 Mark Thomas : >> >> On 19/05/17 23:19, Christopher Schultz wrote: >> >> >> >> > My proposal, adapted from the thread before discussion ceased last >summer: >> > >> > 1. Set Tomcat 8.0.x EOL date for 31 May 2018 >> > 2. Discontinue monthly release cadence for Tomcat 8.0.x after >8.0.45 >> > 3. Make these announcements as soon as we have agreed to the >details for >> > #1 and #2 >> >> Yet again I managed to respond to the sender rather than the list... >> >> +1, for #1 and #3 assuming that we make this 30 June 2018. >> >> I'm neutral on #2 since it is unlikely to be me doing the releases. >I've >> no objection to monthly releases if someone wants to take that on. I >> suspect every 2 to 3 months would be sufficient. > >In case there are enough people that can test the releases and vote I >can >do the releases for example every 2 months. I will try to test and vote. Felix > >Regards, >Violeta > >> >> Mark >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
Hi, 2017-06-05 16:51 GMT+03:00 Mark Thomas: > > On 19/05/17 23:19, Christopher Schultz wrote: > > > > > My proposal, adapted from the thread before discussion ceased last summer: > > > > 1. Set Tomcat 8.0.x EOL date for 31 May 2018 > > 2. Discontinue monthly release cadence for Tomcat 8.0.x after 8.0.45 > > 3. Make these announcements as soon as we have agreed to the details for > > #1 and #2 > > Yet again I managed to respond to the sender rather than the list... > > +1, for #1 and #3 assuming that we make this 30 June 2018. > > I'm neutral on #2 since it is unlikely to be me doing the releases. I've > no objection to monthly releases if someone wants to take that on. I > suspect every 2 to 3 months would be sufficient. In case there are enough people that can test the releases and vote I can do the releases for example every 2 months. Regards, Violeta > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org >
Re: Timescale for 8.0.x EOL
Le 5/06/2017 à 15:51, Mark Thomas a écrit : > +1, for #1 and #3 assuming that we make this 30 June 2018. > > I'm neutral on #2 since it is unlikely to be me doing the releases. I've > no objection to monthly releases if someone wants to take that on. I > suspect every 2 to 3 months would be sufficient. On the Debian side we'll have to support Tomcat 8.0.x until April 2020 (end of Debian 8 "Jessie" LTS). Tomcat 8.0.x is also part of Ubuntu 16.04 LTS which is supported until April 2021. So if we can at least backport the security fixes a bit longer that would be nice (I can help with the backporting if necessary). Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
On 19/05/17 23:19, Christopher Schultz wrote: > My proposal, adapted from the thread before discussion ceased last summer: > > 1. Set Tomcat 8.0.x EOL date for 31 May 2018 > 2. Discontinue monthly release cadence for Tomcat 8.0.x after 8.0.45 > 3. Make these announcements as soon as we have agreed to the details for > #1 and #2 Yet again I managed to respond to the sender rather than the list... +1, for #1 and #3 assuming that we make this 30 June 2018. I'm neutral on #2 since it is unlikely to be me doing the releases. I've no objection to monthly releases if someone wants to take that on. I suspect every 2 to 3 months would be sufficient. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
All, On 6/21/16 2:26 AM, jean-frederic clere wrote: > On 06/20/2016 12:12 PM, Mark Thomas wrote: >> Since it seems there is some interest in maintaining 8.0.x beyond >> September, how about we announce that: >> - the monthly release cycle for 8.0.x will end in September >> - new features and bug fixes are unlikely to be back-ported from that >> point >> - security fixes will probably be back-ported >> - further releases will depend on circumstances but are unlikely to be >> more frequent that 6 monthly > > +1 I will try to find the cycles to be the RM from September on. I forgot that we had had this discussion last year, but this topic came back up at this week's TomcatCon. I believe this was the general consensus from the community present this week: 1. Tomcat 7.0.x is expected to be supported beyond the EOL for Tomcat 8.0.x. I don't believe there were any plans to sundown 7.0.x before 8.0.x, so this isn't a problem. 2. Tomcat 8.5.x should be a "nearly" drop-in replacement for Tomcat 8.0.x. Anything that prevents it from being so should be considered a bug in Tomcat 8.5.x and should be fixed. There are one or two things that could be changed in Tomcat 8.5.x to improve the current situation. 3. A migration guide pointing-out those items which can lead to Tomcat 8.5.x not being a drop-in replacement for Tomcat 8.0.x would be greatly appreciated. Chris Schultz has graciously been voluntold to draft such a guide. NB http://tomcat.apache.org/migration-85.html is too verbose; users are looking for a "these items need to be addressed in order to do a drop-in upgrade" kind of guide. The full migration guide can be used when things don't work well after the short-short version. 4. Setting a definite EOL date is helpful because many vendors will not even consider upgrading from e.g. 8.0.x -> 8.5.x unless there is an EOL on the horizon. In order to force users to upgrade, we may be forced to set this date as aggressively as possible. Conversely, 12 months is about the amount of time that would be required for most users to plan, test, and make the switch. Given the above, I think it's probably safe to re-start the conversation about setting an EOL date for Tomcat 8.0.x. My proposal, adapted from the thread before discussion ceased last summer: 1. Set Tomcat 8.0.x EOL date for 31 May 2018 2. Discontinue monthly release cadence for Tomcat 8.0.x after 8.0.45 3. Make these announcements as soon as we have agreed to the details for #1 and #2 -chris signature.asc Description: OpenPGP digital signature
Re: Timescale for 8.0.x EOL
On 06/20/2016 12:12 PM, Mark Thomas wrote: > Since it seems there is some interest in maintaining 8.0.x beyond > September, how about we announce that: > - the monthly release cycle for 8.0.x will end in September > - new features and bug fixes are unlikely to be back-ported from that > point > - security fixes will probably be back-ported > - further releases will depend on circumstances but are unlikely to be > more frequent that 6 monthly +1 I will try to find the cycles to be the RM from September on. Cheers Jean-Frederic - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
2016-06-20 19:12 GMT+09:00 Mark Thomas: > > > Since it seems there is some interest in maintaining 8.0.x beyond > September, how about we announce that: > - the monthly release cycle for 8.0.x will end in September > - new features and bug fixes are unlikely to be back-ported from that > point > - security fixes will probably be back-ported > - further releases will depend on circumstances but are unlikely to be > more frequent that 6 monthly > > +1 > Mark > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- > Keiichi.Fujino > > >
Re: Timescale for 8.0.x EOL
Am 20.06.2016 um 12:12 schrieb Mark Thomas: On 15/06/2016 08:02, jean-frederic clere wrote: On 06/14/2016 02:05 PM, Rémy Maucherat wrote: 2016-06-14 10:31 GMT+02:00 Mark Thomas: On 14/06/2016 09:00, Emmanuel Bourg wrote: Le 13/06/2016 à 17:47, Mark Thomas a écrit : Now we have a stable release of 8.5.x, I'd like to finialise the end of life date for 8.0.x so we can publish it. We originally said we'd do parallel releases for 6 months. That gives an EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. Any objections to that date or suggestions for a better one? Hi, Just a word with my Debian maintainer hat on, Tomcat 8.0.x was shipped with Debian 8 Jessie with the expectation it would be supported during the lifetime of this release (until May 2018). I'm currently maintaining with other volunteers a stable version based on 8.0.14 (with backported security patches). Canonical does a similar job for Ubuntu 16.04 LTS based on Tomcat 8.0.32. The early EOL of 8.0.x is impractical because, at least in Debian, major updates like the switch to 8.5 aren't allowed for the stable distribution. I understand you can't maintain so many branches for a long time, but if Tomcat 8.0.x could be security supported at least until the Debian 9 release (~April/May 2017) it would allow users following the stable distribution to remain on a supported version of Tomcat (Debian 9 will include Tomcat 8.5). That is unlikely unless someone volunteers for that task. Yes JF or myself could volunteer to do some additional limited 8.0 releases, but we'll see how it goes in practice. We have to provide long term support for our customers, one way is to keep 8.0.x alive here so the community can benefit our efforts. Since it seems there is some interest in maintaining 8.0.x beyond September, how about we announce that: - the monthly release cycle for 8.0.x will end in September - new features and bug fixes are unlikely to be back-ported from that point - security fixes will probably be back-ported - further releases will depend on circumstances but are unlikely to be more frequent that 6 monthly Maybe we don't need to be too specific on the expected interval (just dropping "but are unlikely to be more frequent that 6 monthly"). But I'm +1 with and without this variation. Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
2016-06-20 13:12 GMT+03:00 Mark Thomas: > On 15/06/2016 08:02, jean-frederic clere wrote: >> On 06/14/2016 02:05 PM, Rémy Maucherat wrote: >>> 2016-06-14 10:31 GMT+02:00 Mark Thomas : >>> On 14/06/2016 09:00, Emmanuel Bourg wrote: > Le 13/06/2016 à 17:47, Mark Thomas a écrit : >> Now we have a stable release of 8.5.x, I'd like to finialise the end of >> life date for 8.0.x so we can publish it. >> >> We originally said we'd do parallel releases for 6 months. That gives an >> EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. >> >> Any objections to that date or suggestions for a better one? > > Hi, > > Just a word with my Debian maintainer hat on, Tomcat 8.0.x was shipped > with Debian 8 Jessie with the expectation it would be supported during > the lifetime of this release (until May 2018). I'm currently maintaining > with other volunteers a stable version based on 8.0.14 (with backported > security patches). Canonical does a similar job for Ubuntu 16.04 LTS > based on Tomcat 8.0.32. > > The early EOL of 8.0.x is impractical because, at least in Debian, major > updates like the switch to 8.5 aren't allowed for the stable distribution. > > I understand you can't maintain so many branches for a long time, but if > Tomcat 8.0.x could be security supported at least until the Debian 9 > release (~April/May 2017) it would allow users following the stable > distribution to remain on a supported version of Tomcat (Debian 9 will > include Tomcat 8.5). That is unlikely unless someone volunteers for that task. >>> >>> Yes JF or myself could volunteer to do some additional limited 8.0 >>> releases, but we'll see how it goes in practice. >> >> We have to provide long term support for our customers, one way is to >> keep 8.0.x alive here so the community can benefit our efforts. > > Since it seems there is some interest in maintaining 8.0.x beyond > September, how about we announce that: > - the monthly release cycle for 8.0.x will end in September > - new features and bug fixes are unlikely to be back-ported from that > point > - security fixes will probably be back-ported > - further releases will depend on circumstances but are unlikely to be > more frequent that 6 monthly +1 Generally our good practice thus far was to give a notice 1 year ahead of EOL of a version of Tomcat. This plan is aligned with that practice, so I like it. "6 months" sounds too harsh. I think 3 months, or "3 - 6" months. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
2016-06-20 13:12 GMT+03:00 Mark Thomas: > > On 15/06/2016 08:02, jean-frederic clere wrote: > > On 06/14/2016 02:05 PM, Rémy Maucherat wrote: > >> 2016-06-14 10:31 GMT+02:00 Mark Thomas : > >> > >>> On 14/06/2016 09:00, Emmanuel Bourg wrote: > Le 13/06/2016 à 17:47, Mark Thomas a écrit : > > Now we have a stable release of 8.5.x, I'd like to finialise the end of > > life date for 8.0.x so we can publish it. > > > > We originally said we'd do parallel releases for 6 months. That gives an > > EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. > > > > Any objections to that date or suggestions for a better one? > > Hi, > > Just a word with my Debian maintainer hat on, Tomcat 8.0.x was shipped > with Debian 8 Jessie with the expectation it would be supported during > the lifetime of this release (until May 2018). I'm currently maintaining > with other volunteers a stable version based on 8.0.14 (with backported > security patches). Canonical does a similar job for Ubuntu 16.04 LTS > based on Tomcat 8.0.32. > > The early EOL of 8.0.x is impractical because, at least in Debian, major > updates like the switch to 8.5 aren't allowed for the stable > >>> distribution. > > I understand you can't maintain so many branches for a long time, but if > Tomcat 8.0.x could be security supported at least until the Debian 9 > release (~April/May 2017) it would allow users following the stable > distribution to remain on a supported version of Tomcat (Debian 9 will > include Tomcat 8.5). > >>> > >>> That is unlikely unless someone volunteers for that task. > >>> > >> > >> Yes JF or myself could volunteer to do some additional limited 8.0 > >> releases, but we'll see how it goes in practice. > > > > We have to provide long term support for our customers, one way is to > > keep 8.0.x alive here so the community can benefit our efforts. > > Since it seems there is some interest in maintaining 8.0.x beyond > September, how about we announce that: > - the monthly release cycle for 8.0.x will end in September > - new features and bug fixes are unlikely to be back-ported from that > point > - security fixes will probably be back-ported > - further releases will depend on circumstances but are unlikely to be > more frequent that 6 monthly +1 Regards, Violeta > Mark > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org >
Re: Timescale for 8.0.x EOL
2016-06-20 12:12 GMT+02:00 Mark Thomas: > Since it seems there is some interest in maintaining 8.0.x beyond > September, how about we announce that: > - the monthly release cycle for 8.0.x will end in September > - new features and bug fixes are unlikely to be back-ported from that > point > - security fixes will probably be back-ported > - further releases will depend on circumstances but are unlikely to be > more frequent that 6 monthly > > +1 Rémy
Re: Timescale for 8.0.x EOL
On 15/06/2016 08:02, jean-frederic clere wrote: > On 06/14/2016 02:05 PM, Rémy Maucherat wrote: >> 2016-06-14 10:31 GMT+02:00 Mark Thomas: >> >>> On 14/06/2016 09:00, Emmanuel Bourg wrote: Le 13/06/2016 à 17:47, Mark Thomas a écrit : > Now we have a stable release of 8.5.x, I'd like to finialise the end of > life date for 8.0.x so we can publish it. > > We originally said we'd do parallel releases for 6 months. That gives an > EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. > > Any objections to that date or suggestions for a better one? Hi, Just a word with my Debian maintainer hat on, Tomcat 8.0.x was shipped with Debian 8 Jessie with the expectation it would be supported during the lifetime of this release (until May 2018). I'm currently maintaining with other volunteers a stable version based on 8.0.14 (with backported security patches). Canonical does a similar job for Ubuntu 16.04 LTS based on Tomcat 8.0.32. The early EOL of 8.0.x is impractical because, at least in Debian, major updates like the switch to 8.5 aren't allowed for the stable >>> distribution. I understand you can't maintain so many branches for a long time, but if Tomcat 8.0.x could be security supported at least until the Debian 9 release (~April/May 2017) it would allow users following the stable distribution to remain on a supported version of Tomcat (Debian 9 will include Tomcat 8.5). >>> >>> That is unlikely unless someone volunteers for that task. >>> >> >> Yes JF or myself could volunteer to do some additional limited 8.0 >> releases, but we'll see how it goes in practice. > > We have to provide long term support for our customers, one way is to > keep 8.0.x alive here so the community can benefit our efforts. Since it seems there is some interest in maintaining 8.0.x beyond September, how about we announce that: - the monthly release cycle for 8.0.x will end in September - new features and bug fixes are unlikely to be back-ported from that point - security fixes will probably be back-ported - further releases will depend on circumstances but are unlikely to be more frequent that 6 monthly Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
On 06/14/2016 02:05 PM, Rémy Maucherat wrote: > 2016-06-14 10:31 GMT+02:00 Mark Thomas: > >> On 14/06/2016 09:00, Emmanuel Bourg wrote: >>> Le 13/06/2016 à 17:47, Mark Thomas a écrit : Now we have a stable release of 8.5.x, I'd like to finialise the end of life date for 8.0.x so we can publish it. We originally said we'd do parallel releases for 6 months. That gives an EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. Any objections to that date or suggestions for a better one? >>> >>> Hi, >>> >>> Just a word with my Debian maintainer hat on, Tomcat 8.0.x was shipped >>> with Debian 8 Jessie with the expectation it would be supported during >>> the lifetime of this release (until May 2018). I'm currently maintaining >>> with other volunteers a stable version based on 8.0.14 (with backported >>> security patches). Canonical does a similar job for Ubuntu 16.04 LTS >>> based on Tomcat 8.0.32. >>> >>> The early EOL of 8.0.x is impractical because, at least in Debian, major >>> updates like the switch to 8.5 aren't allowed for the stable >> distribution. >>> >>> I understand you can't maintain so many branches for a long time, but if >>> Tomcat 8.0.x could be security supported at least until the Debian 9 >>> release (~April/May 2017) it would allow users following the stable >>> distribution to remain on a supported version of Tomcat (Debian 9 will >>> include Tomcat 8.5). >> >> That is unlikely unless someone volunteers for that task. >> > > Yes JF or myself could volunteer to do some additional limited 8.0 > releases, but we'll see how it goes in practice. We have to provide long term support for our customers, one way is to keep 8.0.x alive here so the community can benefit our efforts. Cheers Jean-Frederic - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
2016-06-14 10:31 GMT+02:00 Mark Thomas: > On 14/06/2016 09:00, Emmanuel Bourg wrote: > > Le 13/06/2016 à 17:47, Mark Thomas a écrit : > >> Now we have a stable release of 8.5.x, I'd like to finialise the end of > >> life date for 8.0.x so we can publish it. > >> > >> We originally said we'd do parallel releases for 6 months. That gives an > >> EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. > >> > >> Any objections to that date or suggestions for a better one? > > > > Hi, > > > > Just a word with my Debian maintainer hat on, Tomcat 8.0.x was shipped > > with Debian 8 Jessie with the expectation it would be supported during > > the lifetime of this release (until May 2018). I'm currently maintaining > > with other volunteers a stable version based on 8.0.14 (with backported > > security patches). Canonical does a similar job for Ubuntu 16.04 LTS > > based on Tomcat 8.0.32. > > > > The early EOL of 8.0.x is impractical because, at least in Debian, major > > updates like the switch to 8.5 aren't allowed for the stable > distribution. > > > > I understand you can't maintain so many branches for a long time, but if > > Tomcat 8.0.x could be security supported at least until the Debian 9 > > release (~April/May 2017) it would allow users following the stable > > distribution to remain on a supported version of Tomcat (Debian 9 will > > include Tomcat 8.5). > > That is unlikely unless someone volunteers for that task. > Yes JF or myself could volunteer to do some additional limited 8.0 releases, but we'll see how it goes in practice. > > > If this isn't possible I'm crossing my fingers and hoping that the 8.5 > > security patches will remain backportable to 8.0.x, and that 8.0.x will > > not be affected by security issues not found in 8.5.x. > > That should be fairly simple. You might need to choose between > back-porting from 8.5.x and forward porting from 7.0.x depending on > where the the problem lies to get the simplest patch but you can always > ask here if you need help. > > I agree, this should produce an easy patch, backwards or forwards will depend on the area of the issue. Obviously that's usually not what people want to hear however, they prefer "we'll support it forever". Rémy
Re: Timescale for 8.0.x EOL
On 14/06/2016 09:00, Emmanuel Bourg wrote: > Le 13/06/2016 à 17:47, Mark Thomas a écrit : >> Now we have a stable release of 8.5.x, I'd like to finialise the end of >> life date for 8.0.x so we can publish it. >> >> We originally said we'd do parallel releases for 6 months. That gives an >> EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. >> >> Any objections to that date or suggestions for a better one? > > Hi, > > Just a word with my Debian maintainer hat on, Tomcat 8.0.x was shipped > with Debian 8 Jessie with the expectation it would be supported during > the lifetime of this release (until May 2018). I'm currently maintaining > with other volunteers a stable version based on 8.0.14 (with backported > security patches). Canonical does a similar job for Ubuntu 16.04 LTS > based on Tomcat 8.0.32. > > The early EOL of 8.0.x is impractical because, at least in Debian, major > updates like the switch to 8.5 aren't allowed for the stable distribution. > > I understand you can't maintain so many branches for a long time, but if > Tomcat 8.0.x could be security supported at least until the Debian 9 > release (~April/May 2017) it would allow users following the stable > distribution to remain on a supported version of Tomcat (Debian 9 will > include Tomcat 8.5). That is unlikely unless someone volunteers for that task. > If this isn't possible I'm crossing my fingers and hoping that the 8.5 > security patches will remain backportable to 8.0.x, and that 8.0.x will > not be affected by security issues not found in 8.5.x. That should be fairly simple. You might need to choose between back-porting from 8.5.x and forward porting from 7.0.x depending on where the the problem lies to get the simplest patch but you can always ask here if you need help. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
Le 13/06/2016 à 17:47, Mark Thomas a écrit : > Now we have a stable release of 8.5.x, I'd like to finialise the end of > life date for 8.0.x so we can publish it. > > We originally said we'd do parallel releases for 6 months. That gives an > EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. > > Any objections to that date or suggestions for a better one? Hi, Just a word with my Debian maintainer hat on, Tomcat 8.0.x was shipped with Debian 8 Jessie with the expectation it would be supported during the lifetime of this release (until May 2018). I'm currently maintaining with other volunteers a stable version based on 8.0.14 (with backported security patches). Canonical does a similar job for Ubuntu 16.04 LTS based on Tomcat 8.0.32. The early EOL of 8.0.x is impractical because, at least in Debian, major updates like the switch to 8.5 aren't allowed for the stable distribution. I understand you can't maintain so many branches for a long time, but if Tomcat 8.0.x could be security supported at least until the Debian 9 release (~April/May 2017) it would allow users following the stable distribution to remain on a supported version of Tomcat (Debian 9 will include Tomcat 8.5). If this isn't possible I'm crossing my fingers and hoping that the 8.5 security patches will remain backportable to 8.0.x, and that 8.0.x will not be affected by security issues not found in 8.5.x. Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Timescale for 8.0.x EOL
Looks good. +1 -- From:Mark ThomasTime:2016 Jun 13 (Mon) 23:47 To:dev@tomcat.apache.org Subject:Timescale for 8.0.x EOL Now we have a stable release of 8.5.x, I'd like to finialise the end of life date for 8.0.x so we can publish it. We originally said we'd do parallel releases for 6 months. That gives an EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. Any objections to that date or suggestions for a better one? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Timescale for 8.0.x EOL
Now we have a stable release of 8.5.x, I'd like to finialise the end of life date for 8.0.x so we can publish it. We originally said we'd do parallel releases for 6 months. That gives an EOL date of 30 September 2016 for 8.0.x which seems reasonable to me. Any objections to that date or suggestions for a better one? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org