Re: [jakartaee-platform-dev] VOTE: Specifications to add in Jakarta EE 9

[Tibor Digana <tibordigana@xxxxxxxxxx>]

>> but part of the transfer

Then please rename the version from 9 to 8.1.

I remember the Vote of users in Java EE Guardians several years ago when we voted for alignment between EE and SE and the release time alignment as well.

IMO the Java Modules would be something very natural in Jakarta EE 9 because not only Maven POM but also the binary file of the API would declare that it is dependent on another API.

It would be clear for the build tool to build the EE application with tailor made container and no list of api-layers would have to be specified by the user in the build tool.

I think this would be a big jump in EE 9 but with SE 9 in the area of Microservices and such profile.

Pls reserve the version number 9 for what i have described, rename this "transfer" release to 8.1 and try to be consistent with the original idea of alignment with SE releases; otherwise the number would be really meaningless.

WBR

Tibor17

On Mon, Nov 18, 2019 at 8:04 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

Hi,

On Mon, Nov 18, 2019 at 5:01 AM Tibor Digana <tibordigana@xxxxxxxxxx> wrote:

The speed is extremely important, otherwise releasing all APIs in the umbrella would make no difference from JCP regarding the speed of release.

True, but notice that this release (Jakarta EE 9) is still in fact not part of the still to be established "normal" cadence, but part of the transfer. This normal cadence should start with Jakarta EE 10, which would be the first feature release after the transfer has fully completed.

Kind regards,

Arjan

  

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev