Emmanuel, On 6/23/17 11:35 AM, Emmanuel Bourg wrote: > Le 23/06/2017 à 16:29, Christopher Schultz a écrit : > >> Can you clarify: you voted to NOT ANNOUNCE Tomcat 8.0 EOL now, but it's >> not very kind to consumers to surprise them in 2018 by saying "security >> patches only" sometime later. >> >> Why not state NOW that we will be EOLing Tomcat 8.0 in 2018 and starting >> NOW we will only provide security patches for it? > > My concern is to keep having security support for Tomcat 8.0.x because > it will still be used by Linux distributions beyond June 2018 (and > probably others). Tomcat 8.0.x will be only 4 years old at this date, > that's a rather short life by Tomcat standards. > > I wouldn't mind if feature updates stopped right now and if 8.0.x > received only security updates from now on (be it EOLed next year or > not). That would simplify the maintenance and encourage people to > upgrade to 8.5.
The idea was to encourage package repository maintainers to migrate to Tomcat 8.5. If we never sundown Tomcat 8.0, they'll never move (witness the presence of Tomcat 6.0 still lurking around half the Internet). -chris
signature.asc
Description: OpenPGP digital signature
