I started on the steps for the final
checklist and was able to get further with some than others,
For item 1, I submitted the Jenkins job to
release to Maven, which it claims was successful,
https://ci.eclipse.org/cu/view/Release/job/Release%20API%20to%20Maven%20Central/30/
However, that was a number of hours ago and
I still don’t see a 3.0.0 on
https://mvnrepository.com/artifact/jakarta.enterprise.concurrent/jakarta.enterprise.concurrent-api
But I can directly download artifacts if I
take some of the 2.0.0 links and replace 2.0.0 with 3.0.0, so
it seems like it at least partly worked,
https://repo1.maven.org/maven2/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-api/3.0.0/jakarta.enterprise.concurrent-api-3.0.0.jar
https://repo1.maven.org/maven2/jakarta/enterprise/concurrent/jakarta.enterprise.concurrent-tck/3.0.0/jakarta.enterprise.concurrent-tck-3.0.0.jar
Could someone confirm if the Jenkins job
worked properly or if it needs to be fixed?
For item 2, the links on https://jakarta.ee/specifications/concurrency/3.0/
are working except for the TCK and SHA links.
Here is the current location (working),
https://download.eclipse.org/ee4j/cu/jakartaee10/promoted/eftl/concurrency-tck-3.0.0.zip
versus the linked location (not working),
https://download.eclipse.org/jakartaee/concurrency/3.0/jakarta-concurrency-tck-3.0.0.zip
Item 3 is not applicable because this spec
doesn’t have its own schemas.
For item 4, approve the compatibility
request, does this just involve adding the accepted label to
https://github.com/jakartaee/concurrency/issues/175
(the compatibility certification request) and closing it? I’d
do that myself except I was the one who opened the request and
it seems odd that the same person who opened it would also
accept it. Maybe this should be done by the spec lead (Steve)
?
For item 5, I have sent the email to tck@xxxxxxxxxxx on behalf
of Open Liberty.
For item 6, we weren’t using a separate
release branch so there is no merging to be done. I did
create
https://github.com/jakartaee/concurrency/releases/tag/3.0.0
from the tag
https://github.com/jakartaee/concurrency/releases/tag/3.0.0
combining part of the generated release notes and based on the
new features list from
https://jakarta.ee/specifications/concurrency/3.0/
. I’m unsure if there are other steps to take on the github
side.
My thanks and
congratulations to the team on the successful conclusion
of the release review ballot for Jakarta Concurrency 3.0.
I've created a final check-list issue to guide you through
the final steps necessary to wrap this release up:
|
This
Message Is From an External Sender
|
|
This
message came from outside your
organization.
|
|
|
My thanks and congratulations to the team on the successful
conclusion of the release review ballot for Jakarta
Concurrency 3.0. I've created a final check-list issue to
guide you through the final steps necessary to wrap this
release up:
https://github.com/jakartaee/concurrency/issues/219
Once the artifacts are pushed to Maven, please let me know
and I can finish the final tidy-up of the released
specification page (currently in
this PR).
Again, thank you all for your diligence and for working
through the steps necessary for getting this new version
finalized.
-- Ed Bratt
On 4/27/2022 1:32 PM, Ed Bratt wrote:
Hi There,
Just wanted to let you know that I've started the release
review ballot. thank you very much for attending to all the
requests I've made on behalf of the Spec. committee.
Please let me know if anything comes up that might require
an update. We'd need to cancel the current review ballot and
start it over if that were to happen (Spec. document, TCK).
If you are interested, you can follow the ballot on the
public Jakarta EE discussion list:
jakarta.ee-spec@xxxxxxxxxxx.
The thread starts from
this message.
For your planning, there will be one more checklist to work through,
once the ballot is completed -- Generally, this is just the
usual "finish it all up" stuff that will allow us complete
close out this version release.
On behalf of the Spec. committee, my sincere thanks to you
all for getting us this far. A bit more to go and we'll be
able to put a bow on this.
-- Ed Bratt
_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev
