| Re: [ee4j-pmc] JAX-RS API Release |
How will the simultaneous release synchronization happen? Do I have to press the trigger at some to-be-announced time? I do not understand why JAX-RS API must wait for other projects. We do not depend on much. Why shall users of JAX-RS API wait for an artifically set sync date (possibly months ago)? That feels like an unnecessary obstacle. -Markus From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of dmitry.kornilov@xxxxxxxxxx The general release workflow is described here: I put that link to the task I created. In case you didn't read it copying here: General Workflow 1. Release all projects to OSSRH staging repository. 2. Apply for release reviews. Instructions are below. 3. When all components are deployed, simultaneous release review will happen. 4. After passing all CTS/TCK tests, all components will be released to Maven Central. Does it answer your questions? -- Dmitry От: Markus KARG Отправлено: пятница, 17 августа, 8:31 Тема: Re: [ee4j-pmc] JAX-RS API Release Кому: 'EE4J PMC Discussions' Sorry Ed, but this answer simply is not sufficient. "I believe" and "I think" are no reliable enough terms. We need to really have legal certainty before the release. It shouldn't be too hard for the Oracle and EF lawyers to simply pick up the phone right now, discuss this issue, agree on YES or NO, and clearly answer the original question today without any whens or ifs or shoulds or coulds: "YES, JAX-RS API 2.1.1 MAY be released immediately" or "NO, JAX-RS API 2.1.1 MUST NOT be released immediately" Sorry for being persistent, but either I MAY press the button today or I MUST NOT. -Markus BTW, I know you all mean well, but please understand that I do not wanted a fire up a discussion, but that the aim of my question was an OFFICIAL and LEGALLY UNDISPUTED answer from the PMC, EMO, Mike, or that Oracle lawyer that definitively is eligible to finally answer it. If this is Ed, then it must be told clearly. From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Ed Bratt Sent: Donnerstag, 16. August 2018 23:54 To: EE4J PMC Discussions; David Blevins Subject: Re: [ee4j-pmc] JAX-RS API Release David (and PMC): (Jumping in because Dmitry is on holiday.) I believe that these are the "equivalence" releases for Eclipse GlassFish 5.1. The goal with this first set of Eclipse Jakarta EE components is that they have exactly the same API compatibility as those used in GlassFish 5.0 (i.e. both are Java EE 8 compatible). Since they will be tested and certified for compatibility, I believe that this is fully in compliance with the terms of the TCK agreements that are to be signed. Further, I think this is within the scope of agreements already in place since no specified APIs are changed. I have asked Oracle developers to perform TCK verification for any components ready for Eclipse Release Review before the TCK agreement with Eclipse Foundation is signed. The TCK agreement must be finished before we can finalize Eclipse GlassFish 5.1 and use any Java EE branding. We are working to complete that discussion. Once the agreement is in place, we can do this compatibility testing on Eclipse resources. I thought that we'd discussed this at Steering Committee, but perhaps not clearly enough. I'd be happy to answer additional questions, here in e-mail, or at the meeting. Cheers, -- Ed Bratt On 8/16/2018 2:32 PM, David Blevins wrote:
|