Re: [cu-dev] Checking in -- progress towards finishing Concurrency Utili

["Nathan Rauh" <nathan.rauh@xxxxxxxxxx>]

I can help provide
some of the estimated timeline assuming that we will need to use Open Liberty
as the compatible implementation upon which to certify.  Toward the
end of last year I sent an email out querying if there were any other implementations
that could be used as the compatible implementation that would meet the
Feb 28 deadline, and thus far haven't heard back from any others.

Here's how the
schedule would line up:

The pull to port
over the old TCK bucket to the Concurrency project and merge it with the
new TCK tests that have already been written for Concurrency 3.0 is currently
in review state.  It appears that all of the review comments thus
far have been very minor and so I expect it to be merged relatively soon,
probably within the next few days.

After this, one
of the participants is working on a remaining new TCK test to include the
new resource definition annotations on an EJB.  That will need to
be submitted, reviewed and merged, hopefully early next week.

After that, an
official RC1 build will need to be performed, and the spec API jar and
TCK jar published to maven.  I have no idea how to do either of these
things, but hopefully Steve knows or either of you who are helping to mentor
will know and can help with it.

If that can all
be done by January 19, then we should be able to get it into the next beta
release of Open Liberty.
Every day beyond
that point over the next week will have an increasingly lesser chance of
making the February beta. I don't expect Open Liberty will hold up or change
its release schedule for just this spec.

When the February
beta comes out around the beginning of February, then we would be able
to collect official results of the TCK running with the 3.0 RC1 release
on the Open Liberty beta as the compatible implementation.  It will
take several days further to get those results published to a publically
accessible location, but it would be well before the Feb 28 deadline.

The main risk
here is getting the 3.0 RC1 image created and published to Maven in time.


If another implementation
with a more flexible schedule or more lenient approach to certification
comes along, that would certainly help add some time.  But absent
that, we do at least have a path to meeting Feb 28, albeit a narrow one.




From:
       "Ed
Bratt" <ed.bratt@xxxxxxxxxx>
To:
       "cu
developer discussions" <cu-dev@xxxxxxxxxxx>, "Steve Millidge
(Payara)" <steve.millidge@xxxxxxxxxxx>
Cc:
       "DMITRY.KORNILOV"
<dmitry.kornilov@xxxxxxxxxx>
Date:
       01/12/2022
11:55 AM
Subject:
       [EXTERNAL]
[cu-dev] Checking in -- progress towards finishing Concurrency Utilities
3.0?
Sent
by:        "cu-dev"
<cu-dev-bounces@xxxxxxxxxxx>

---

Hi,

Dmitry Kornilov and I have been assigned by the Specification Committee
to mentor you through the process of finalizing the Release PR for the
upcoming release review of Jakarta Concurrency 3.0 for inclusion in EE10.

As a part of wave 1 in the Jakarta
EE 10 Release Plan, the release
review PR could be made at any time. You may create the PR even if you
don't have all the information required. Just mark it as DRAFT and work
on it together with your mentor (me).

Are you on track with finishing up this
specification version and creating a PR for this specification in the specificationsrepository? Are you able to estimate when the team anticipates starting
this final step?
Is there anything blocking/delaying the
release?
Is there anything Dmitry or I can help
you or the project team with?
Thank you,
-- Ed_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev