That's good feedback, and much appreciated. I have a couple of things to clear "right now", but then I should be back onto working on Java 11 support. Its likely that I'll work on that as opposed to TomEE 8 / MP, and time permitting, I'd like to work on MP / Jakarta EE items after the J11 support.
Long story short though, I believe there are people to work on the various items, and I'm sure those things can happen in parallel. Specifically, there is a concern that if lots of people work on TomEE 7.1.x, progress is slowed on TomEE 8, and if I'm reading the feedback correctly, some folks would prefer to drop TomEE 7.1.x altogether. Personally, I think those working on MP / Jakarta EE items should be free to do so, with the guidance of "please commit to master first". Importantly though, if they wish to backport to another branch, they should not be prevented from doing so. Similarly, I want to work on Java 11 support. I too will commit that to master, but I'd certainly want to backport that support as far back as 1.7.x if it is possible, and I feel I shouldn't be prevented from doing so. Hopefully that provides some re-assurance about commitment to Java 11, and some clarification around the VOTE. Jon On Thu, Aug 9, 2018 at 12:39 PM, Alex The Rocker <[email protected]> wrote: > Non-binding: > > -1 : if there's a lack of resource i'd prefer to see first TomEE > compatibility with Java 11 LTS addressed as soon as possible (hoping a > fix for at least https://issues.apache.org/jira/browse/TOMEE-2200...). > > Indeed, Java 11 LTS is supposed to be soon available (25/09 according > to http://openjdk.java.net/projects/jdk/11/) and most major projects > (Hadoop, etc.) are waiting for this LTS (Long Term Support) version to > move beyond Java 8. > > I have the felling that any major release from TomEE arriving > somewhere in November should be as ready as possible to live with this > "new Java for the couple of upcoming years..." > > Thanks, > Alexandre > Le jeu. 9 août 2018 à 08:09, David Blevins <[email protected]> a > écrit : > > > > For a few months we've discussed doing and not doing a TomEE 7 flavored > release of MicroProfile 1.x for Java EE 7 users on Java 8, tentatively > versioned TomEE 7.1. > > > > Earliest email with TomEE 7.1 in the subject is around April, though I > vaguely recall it mentioned before. I recall seeing a request from Mark to > wait on it till after 7.0.5 was released. That's now out and a TomEE 7.1.x > branch has been created and being actively worked on. > > > > There seem to be concerns that this will draw attention away from TomEE > 8, which is understandable, and some sentiment that this work should stop > and everyone focus on TomEE 8. I haven't seen anyone suggest not working > on TomEE 8, so I'll assume that as a constant that doesn't need to be voted > on. > > > > As the concern is largely resources, I propose the following compromise: > > > > - MicroProfile related PRs that can possibly apply to TomEE 8 must be > merged to master *before* the equivalent can be merged to TomEE 7.1.x. In > short, everyone must work on TomEE 8. > > > > - Those who wish to focus time only on TomEE 8 may do so, someone else > can merge the PR to 7.1.x if they have the energy. In short, only the > willing need work on TomEE 7.1.x > > > > With this in mind, the vote: > > > > +1 Allow work on TomEE 7.1 to proceed with the above two conditions > > +-O Abstain or don't feel strongly > > -1 I have a better idea > > > > > > > > -David > > >
