Le 19 avr. 2018 20:47, "Mark Struberg" <[email protected]> a écrit :
Heh that was nicely put and I do certainly agree with your finding ;) @Romain, the 7.1 was just 7.0.x + java8 bump and MP. I got that but not its need. Of course I have no clue who will use EE7 with MP, if he can have EE8 as well... All I wanted is to make a clear disctinction between TomEE with Java7 and TomEE which requires Java8 - thus the required bump to 7.1.x. Hmm, technically we know how to do a 7.0 with a mp distro (all but mp on java 7). Im not against a 7.1 but if it only brings 10% of a MP distro im not convinced it is wise to do it. Writing I even wonder if MP justifies a minor bump. Our online versioning policy references minor as a feature level marker. MP distro doesnt bring any feature to most tomee users - as well as just a java min version bump - so arent we too enthusiast here? The important thing to keep in mind is users, not tech choices. Just my 2cts indeed LieGrue, strub > Am 19.04.2018 um 13:23 schrieb Rudy De Busscher <[email protected]>: > > If needed, I can lend a hand in updating TomEE 7.1 > > But I agree, certification becomes less an issue.I have the impression > that even Big vendors don't set it as a priority. > > Rudy > > On 19 April 2018 at 11:24, Mark Struberg <[email protected]> wrote: > >> Of course having a TomEE-7.1 which bumps the requirement to java8 is cool. >> And I fully support that. >> But right now let's please focus on shipping TomEE-7.0.5 first. >> Most probably 7.1 could be done almost in parallel. >> But we do not have endless resources. At least I don't. >> >> LieGrue, >> strub >> >>> Am 19.04.2018 um 05:25 schrieb David Blevins <[email protected]>: >>> >>> >>>> On Apr 18, 2018, at 4:08 AM, Mark Struberg <[email protected]> >> wrote: >>>> >>>> There was a discussion about this a few weeks ago where we agreed to >> ship TomEE-7.0.5 and only then switch to a branch. >>>> >>>> That's the reason why we backported tons of stuff in Johnzon, OWB and >> OpenJPA. >>>> Just waiting for feedback whether it now works fine or if there is >> still something broken. >>>> >>>> So my suggestion is to apply this to the TomEE8 branch and wait with >> the other PR until TomEE-7.0.5 is released. >>> >>> Kicked off a proper "Status of TomEE 8" thread so we can have a full >> conversation on what to do with TomEE 8. >>> >>> If people were willing to put the effort into a TomEE 7.1 in addition to >> whatever is decided in that thread, would you be ok with a TomEE 7.1 as >> well? >>> >>> For context: I know Jean-Louis is heading off to Brazil in May to do a >> TomEE talk that shows his JWT work. Ideally he's not showing a snapshot >> and people could leave with something they can try. He's doing that talk >> again in June. >>> >>> My personal perspective is if the decision was made to release TomEE 8 >> now, I'd still see value in a 7.1 release with MicroProfile as then the >> users would have the choice. Some may not want to do a Java EE 7 to Java >> EE 8 upgrade, but still want to enjoy some MicroProfile technologies. >>> >>> >>> -David >>> >>> >>> >> >>
