Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [BALLOT] Proposal for bringing EE 11 Web and Platform specs to ballot by end of CY 2024
Hi,

On Fri, 29 Nov 2024 at 12:35, Emily Jiang via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
If we execute this proposal, we might get EE 11 released earlier

Just a small reminder, we will never be able to release EE 11 earlier. We're already half a year later than planned and promised.
 
but I think it will damage the brand by sending a worrying message to the end users

Not releasing will also send a worrying message, namely that Jakarta EE is dead. On an almost daily basis I see companies migrating to Spring Boot, since their perception is that Jakarta EE is dead (which is primarily based by it not releasing any new features in the large time frame between Java EE 8 and Jakarta EE 10).

and the Jakarta EE community might have to deal with a much bigger penalty later.

My 2 cents: nobody will notice anything about app client tests.

Kind regards,
Arjan Tijms

 

Thanks,
Emily

On Tue, Nov 26, 2024 at 2:13 PM Ed Burns via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:

Executive summary


A +1 vote means you, as a Platform Project committer, agree we, as the Platform Project, will submit by 2024-12-27 the ballots for EE 11 Web and Platform profiles with a TCK exclusion list containing all the non-passing appclient tests as of 2024-12-15.

Details


Greetings programs,


As discussed at the 2024-11-19 platform project call (agenda) and discussed at the 2024-11-20 platform TCK project call (agenda), and in my capacity as release co-coordinator for Jakarta EE 11, I am calling a fourteen day BALLOT among platform project members on how we will meet the deadline of submitting the Web and Platform profile ballots before end of CY-2024. If this BALLOT passes, according to the traditional process we use of counting binding votes, the platform project will proceed with producing the artifacts to submit the Web and Platform artifacts to the specification committee as described in the proposal below.

This proposal assumes the platform TCK project can get all non-app client Jakarta EE 11 platform TCK tests passing against the GLASSFISH_8_0_JDK_17 branch when run with Java SE 17 and Java SE 21. If the platform TCK is not able to satisfy this assumption, this proposal is moot.


The proposal is:

  • The Jakarta EE 11 Platform TCK is the fully refactored TCK. None of this hybrid business where we use the EE 10 Platform TCK for some of the tests, and the EE 11 Platform TCK for the rest of them.
  • All app client tests for all vehicles and component sub-modules that are not running by 2024-12-15 are added to the exclusion list.

We start the ballots for Platform and Web by 2024-12-27.


This ballot will run for fourteen consecutive calendar days from the date of this email.

We will count the +1, 0, and -1 votes from all committers to the platform project as "binding" votes. Any other +1, 0, and -1 votes will count as "non-binding" votes. Only the "binding" votes will be considered to decide if the ballot passes. This is exactly the same process the platform project used in 2023-07 when deciding which specs to include in EE 11. For example: Jakarta Data: https://www.eclipse.org/lists/jakartaee-platform-dev/msg04245.html


Thanks,

Ed
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev


--
Thanks
Emily

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top