Re: [cu-dev] Draft release plan for Concurrency 3.1 for EE 11

[Arjan Tijms <arjan.tijms@xxxxxxxxxxx>]

Hi,

The plan looks good. I do wonder if we're able to achieve all of that, but of course teams don't have to achieve everything that's in the plan.

p.s. I've already looked at a CDI based @Lock replacement from the plan, and at the moment the code I have even passed the main EJB Lite test for that feature. I can do a PR to propose that to the API and to the Eclipse Concurro implementation.

Kind regards,

Arjan Tijms

On Thu, 23 Mar 2023 at 20:53, Nathan Rauh <nathan.rauh@xxxxxxxxxx> wrote:

On the Jakarta EE platform calls, they’ve been asking for release plans to be created by all Jakarta EE component specs that will have new releases in Jakarta EE 11.  I noticed that Concurrency didn’t have one, so I created a draft here to get started,
https://projects.eclipse.org/projects/ee4j.cu/releases/3.1/plan

I tried to write some categories there summarizing areas that seem to be the focus of the open issues list for Concurrency.  This can all be changed.

 

The draft release plan required specifying a release date, which I arbitrarily listed as a date near the end of the planned EE 11 release cycle for component specs (currently 4Q2023).  Steve, please go ahead and switch this to the actual release date that you would like.

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