Thanks Nathan looks good. I think the target date is a good one as well as will give time for implementations to test the new spec and make any test updates etc. well before the Jakarta EE 11 target
release date.
Steve Millidge
Director and Founder
Payara -
Supported Enterprise Software for Jakarta EE and MicroProfile Applications
UK:+44 800 538 5490 | Int: +1 888 239 8941
----------------------------------------------------------------------------------------------------------------------
Payara is a proud recipient of the prestigious
Queen's Award for Enterprise: International Trade 2021
Payara Services Limited,
Registered office: Unit 11, Malvern Hills Science Park,
Geraldine Road,
Malvern,
WR14 3SZ
Registered in England and Wales: 09998946 | VAT: GB 193854467 | www.payara.fish
| info@xxxxxxxxxxx
| @Payara_Fish
If at any time you would like to unsubscribe from Payara communications, simply respond to this email
with 'Unsubscribe' in the title, or instantly unsubscribe from all types of communication
here.
From: cu-dev <cu-dev-bounces@xxxxxxxxxxx>
On Behalf Of Nathan Rauh
Sent: Wednesday, March 22, 2023 8:23 PM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: [cu-dev] Draft release plan for Concurrency 3.1 for EE 11
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.