Re: [VOTE] 8.0.x EOL - 30 June 2018

On 22/06/17 16:18, Mark Thomas wrote: > We had a couple of threads discussing this. I think it is time for a vote. > > [X] +1 We should announce 8.0.x EOL for 30 June 2018 > [ ] -1 We should announce 8.0.x EOL for [insert date here] > [ ] -1 We should not announce 8.0.x EOL at this time Mark

Re: [VOTE] 8.0.x EOL - 30 June 2018

Hi, The main reason is RFC6265 is released after IE9, and IE9 is still in our supported browser list (though not recommended). I'm personally fine with using LegacyCookieProcessor instead of RFC6265CookieProcessor for LEGACY issues. However, it is not easy for an embedded Tomcat in an

Re: [VOTE] 8.0.x EOL - 30 June 2018

On 26/06/17 13:13, Coty Sutherland wrote: > On Mon, Jun 26, 2017 at 5:51 AM, Mark Thomas wrote: >> On 26/06/17 08:12, Emmanuel Bourg wrote: >>> Le 24/06/2017 à 17:25, Mark Thomas a écrit : >>> If 8.5.x was a drop-in replacement would that make a difference? >>> >>> Yes that

Re: [VOTE] 8.0.x EOL - 30 June 2018

On Mon, Jun 26, 2017 at 5:51 AM, Mark Thomas wrote: > On 26/06/17 08:12, Emmanuel Bourg wrote: >> Le 24/06/2017 à 17:25, Mark Thomas a écrit : >> >>> If 8.5.x was a drop-in replacement would that make a difference? >> >> Yes that would help. >> >> >>> And as a follow-up, what

Re: [VOTE] 8.0.x EOL - 30 June 2018

On 26/06/17 03:19, Huxing Zhang wrote: >> The only thing I can think of is lack of support for the BIO connectors. >> I have an easy fix for that if there is interest. Anything else? > > Also the RFC6265CookieProcessor. We've experienced several incompatibility > with LegacyCookieProcessor. >

Re: [VOTE] 8.0.x EOL - 30 June 2018

On 26/06/17 08:12, Emmanuel Bourg wrote: > Le 24/06/2017 à 17:25, Mark Thomas a écrit : > >> If 8.5.x was a drop-in replacement would that make a difference? > > Yes that would help. > > >> And as a follow-up, what would need to change so 8.5.x was viewed a >> drop-in replacement? > > The

Re: [VOTE] 8.0.x EOL - 30 June 2018

Le 24/06/2017 à 17:25, Mark Thomas a écrit : > If 8.5.x was a drop-in replacement would that make a difference? Yes that would help. > And as a follow-up, what would need to change so 8.5.x was viewed a > drop-in replacement? The removal of the BIO connectors was the main issue reported. It

Re: [VOTE] 8.0.x EOL - 30 June 2018

> The only thing I can think of is lack of support for the BIO connectors. > I have an easy fix for that if there is interest. Anything else? Also the RFC6265CookieProcessor. We've experienced several incompatibility with LegacyCookieProcessor. For example, cookies with leading dot is no

Re: [VOTE] 8.0.x EOL - 30 June 2018

On 23/06/17 23:17, Emmanuel Bourg wrote: > Le 23/06/2017 à 21:15, Christopher Schultz a écrit : > >> 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

Re: [VOTE] 8.0.x EOL - 30 June 2018

Am 22.06.2017 um 17:18 schrieb Mark Thomas: We had a couple of threads discussing this. I think it is time for a vote. [X] +1 We should announce 8.0.x EOL for 30 June 2018 [ ] -1 We should announce 8.0.x EOL for [insert date here] [ ] -1 We should not announce 8.0.x EOL at this time +1

Re: [VOTE] 8.0.x EOL - 30 June 2018

Le 23/06/2017 à 21:15, Christopher Schultz a écrit : > 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). As far as Debian is

Re: [VOTE] 8.0.x EOL - 30 June 2018

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. >>

Re: [VOTE] 8.0.x EOL - 30 June 2018

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

Re: [VOTE] 8.0.x EOL - 30 June 2018

All, On 6/22/17 11:18 AM, Mark Thomas wrote: > We had a couple of threads discussing this. I think it is time for a > vote.> > [X] +1 We should announce 8.0.x EOL for 30 June 2018 > [ ] -1 We should announce 8.0.x EOL for [insert date here] > [ ] -1 We should not announce 8.0.x EOL at this time

Re: [VOTE] 8.0.x EOL - 30 June 2018

Emmanuel, On 6/22/17 11:51 AM, Emmanuel Bourg wrote: > Le 22/06/2017 à 17:18, Mark Thomas a écrit : > >> [X] -1 We should not announce 8.0.x EOL at this time > > I'd prefer security only releases for Tomcat 8.0.x beyond 30 June 2018 > (or even sooner). Can you clarify: you voted to NOT ANNOUNCE

Re: [VOTE] 8.0.x EOL - 30 June 2018

[ X ] +1 We should announce 8.0.x EOL for 30 June 2018 -- From:Mark Thomas Time:2017 Jun 22 (Thu) 23:18 To:Tomcat Developers List Subject:[VOTE] 8.0.x EOL - 30 June 2018 We had a couple of

Re: [VOTE] 8.0.x EOL - 30 June 2018

On Thu, Jun 22, 2017 at 11:18 AM, Mark Thomas wrote: > We had a couple of threads discussing this. I think it is time for a vote. > > [x] +1 We should announce 8.0.x EOL for 30 June 2018 - To unsubscribe,

Re: [VOTE] 8.0.x EOL - 30 June 2018

2017-06-22 10:18 GMT-05:00 Mark Thomas : > We had a couple of threads discussing this. I think it is time for a vote. > > [X] +1 We should announce 8.0.x EOL for 30 June 2018 > [ ] -1 We should announce 8.0.x EOL for [insert date here] > [ ] -1 We should not announce 8.0.x EOL

Re: [VOTE] 8.0.x EOL - 30 June 2018

Le 22/06/2017 à 17:18, Mark Thomas a écrit : > [X] -1 We should not announce 8.0.x EOL at this time I'd prefer security only releases for Tomcat 8.0.x beyond 30 June 2018 (or even sooner). Emmanuel Bourg - To unsubscribe,

Re: [VOTE] 8.0.x EOL - 30 June 2018

Am 22. Juni 2017 17:18:14 MESZ schrieb Mark Thomas : >We had a couple of threads discussing this. I think it is time for a >vote. > >[x] +1 We should announce 8.0.x EOL for 30 June 2018 >[ ] -1 We should announce 8.0.x EOL for [insert date here] >[ ] -1 We should not announce

Re: [VOTE] 8.0.x EOL - 30 June 2018

2017-06-22 18:18 GMT+03:00 Mark Thomas : > > We had a couple of threads discussing this. I think it is time for a vote. > > [X] +1 We should announce 8.0.x EOL for 30 June 2018 > [ ] -1 We should announce 8.0.x EOL for [insert date here] > [ ] -1 We should not announce 8.0.x EOL

Re: [VOTE] 8.0.x EOL - 30 June 2018

On Thu, Jun 22, 2017 at 5:18 PM, Mark Thomas wrote: > We had a couple of threads discussing this. I think it is time for a vote. > > [ X ] +1 We should announce 8.0.x EOL for 30 June 2018 > [ ] -1 We should announce 8.0.x EOL for [insert date here] > [ ] -1 We should not