Re: [DISCUSS] 1.x EOL

Same view here. Fine with me to apply patches (security for instance) but no active development -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, Dec 13, 2018 at 5:41 PM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > My view is still the

Re: [DISCUSS] 1.x EOL

My view is still the same. I'm still willing to patch and release from 1.7.x. At the stage, I don't think we could consider getting it working with Java 11, and I wouldn't actively develop this branch, but I'd be willing to apply fixes and patches to it where possible. Jon On Thu, Dec 13, 2018

Re: [DISCUSS] 1.x EOL

Hi folks, I’m sorry for digging back this old thread. I think we never ended up making a decision on this, and a year and a half as passed since we discussed this. So, I would like to bring to the table again the discussion around supporting TomEE 1.x and EOL. Cheers, Roberto > On 30 Jun

Re: [DISCUSS] 1.x EOL

As mentionned tomcat 8.0 EOL has been announced, here is the interesting part of it: " The Apache Tomcat team announces that support for Apache Tomcat 8.0.x will end on 30 June 2018. This means that after 30 June 2018: - releases from the 8.0.x branch are highly unlikely - bugs affecting only

Re: [DISCUSS] 1.x EOL

2017-06-19 16:04 GMT+02:00 Jonathan Gallimore : > Firstly, I note the page Romain started - thank you for listening to my > feedback. I'd be happy to test instructions and contribute to that page. I > suspect some DBCP(2) settings are different so we should call

Re: [DISCUSS] 1.x EOL

Firstly, I note the page Romain started - thank you for listening to my feedback. I'd be happy to test instructions and contribute to that page. I suspect some DBCP(2) settings are different so we should call those out. I'll also try and help build it out into a step by step guide. Secondly, I

Re: [DISCUSS] 1.x EOL

I read it as: 1. we need 1 year of delay before it is actually EOL - which was the proposal 2. we need doc - which has been done for the known part Concretely I don't see how much it is different from the original plan (which needs to be translated by 1 month now) until there is a *string*

Re: [DISCUSS] 1.x EOL

-1 I would welcome an EOL announcement at the end of the year (with a years notice), but not right now. That's too much pressure. So to make that clear, I would announce EOL on the 1st Jan.18 and EOL is then 1st Jan 2019 - That gives everyone plenty of time to create detailed documentation on the

Re: [DISCUSS] 1.x EOL

http://tomee.apache.org/developer/migration/tomee-1-to-7.html intends to solve that issue, we can add any point we hit/encounter what else would be a blocker to make 1 EOL in June 2018? Romain Manni-Bucau @rmannibucau | Blog

Re: [DISCUSS] 1.x EOL

2017-06-18 19:50 GMT+02:00 Mark Struberg : > regarding migration. > There are 3 different main use cases afaict. > 1.) TomEE standalone server, quite like Tomcat. Using 7.x instead 1.7.x > should be a no-brainer without any need to change something within your >

Re: [DISCUSS] 1.x EOL

regarding migration. There are 3 different main use cases afaict. 1.) TomEE standalone server, quite like Tomcat. Using 7.x instead 1.7.x should be a no-brainer without any need to change something within your application 2.) tomee-maven-plugin: change the groupId from org.apache.openejb to

Re: [DISCUSS] 1.x EOL

I’d be -1 for any kind of EOL of 1.7 right now. -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On Jun 6, 2017, at 8:58 AM, Romain Manni-Bucau wrote: > > Hi guys, > > it is harder and harder to maintain 1.x branch since almost no library is >

Re: [DISCUSS] 1.x EOL

2017-06-18 18:42 GMT+02:00 Jonathan Gallimore : > Thanks for the feedback. I think at least some sort of migration guide is > needed as some settings have changed. It would be nice for people to find > out the easy way. Happy to discuss in another thread, but we should

Re: [DISCUSS] 1.x EOL

Thanks for the feedback. I think at least some sort of migration guide is needed as some settings have changed. It would be nice for people to find out the easy way. Happy to discuss in another thread, but we should agree when this will appear. I also think some visibility on what the EOL

Re: [DISCUSS] 1.x EOL

2017-06-18 17:36 GMT+02:00 Jonathan Gallimore : > On 18 Jun 2017 3:11 pm, "Romain Manni-Bucau" > wrote: > > @Jon: please propose a policy then (same as rejecting a release, "no" is > valid only if an alternative is proposed or a string

Re: [DISCUSS] 1.x EOL

On 18 Jun 2017 3:11 pm, "Romain Manni-Bucau" wrote: @Jon: please propose a policy then (same as rejecting a release, "no" is valid only if an alternative is proposed or a string blocker is found ;)). I feel I stated my concerns pretty clearly. I didn't just reply -1 and

Re: [DISCUSS] 1.x EOL

@Jon: please propose a policy then (same as rejecting a release, "no" is valid only if an alternative is proposed or a string blocker is found ;)). Realisticly 1.7 is no more maintained (the cxf coming exceptional release doesn't help since all the stack is outdated now and coming to EOL and

Re: [DISCUSS] 1.x EOL

So probably one more 1.7.x release and then let it fade out? LieGrue, strub > Am 18.06.2017 um 13:55 schrieb Jonathan Gallimore > : > > I object. There are plenty of folks still using 1.7.x, and we've ported > over various fixes from master without too much

Re: [DISCUSS] 1.x EOL

I object. There are plenty of folks still using 1.7.x, and we've ported over various fixes from master without too much trouble. My concern is that those on 1.7.x might be concerned to see it EOL'd. I'd like to see the upgrade path documented and a policy on fixes applied to 1.7.x documented and

[DISCUSS] 1.x EOL

Hi guys, it is harder and harder to maintain 1.x branch since almost no library is maintained. Request is also decreasing for that version. Tomcat will also EOL tomcat 8 next year (1.x is on tomcat 7 which still dont have an official EOL I think but never good to rely on an outdated version,