Thanks everyone for getting this released!
It seems I was looking at one of the wrong Maven links before. The one that wasn’t initially working was a separate site that indexes into Maven. (It looks like it did eventually update as well and now also shows 3.0.0). Open Liberty
builds are obtaining both the api jar and tck jar from maven now instead of staging, and everything is still building and running cleanly, so the artifacts look good.
From: "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
Date: Friday, May 13, 2022 at 3:27 AM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>, Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Subject: RE: [cu-dev] [External] : Re: : Release Review Successful!
Hi Nathan, The release job worked correctly. All it does is copy from the staging repo in Jakarta.oss.sonatype.org to the release repository. Then it takes some
time to propagate over to maven central. You can check the job worked by looking
|
This Message Is From an External Sender
|
|
This message came from outside your organization.
|
|
|
Hi Nathan,
The release job worked correctly. All it does is copy from the staging repo in Jakarta.oss.sonatype.org to the release repository. Then it takes some time to propagate over to maven central. You can check the job worked by looking in the
release repo.
For Item 6 I created the PR to merge the release branch Release 3.0.0 by smillidge · Pull Request #220 · jakartaee/concurrency (github.com) the release branch is created by the release Jenkins job automatically and creates the tags and branches for the release.
Thanks
Steve
From: cu-dev <cu-dev-bounces@xxxxxxxxxxx>
On Behalf Of Ed Bratt
Sent: 12 May 2022 22:56
To: cu developer discussions <cu-dev@xxxxxxxxxxx>; Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Subject: Re: [cu-dev] [External] : Re: : Release Review Successful!
Nathan,
Concurrency 3.0.0 appears to be pushed to maven. I'm not sure what mechanics are associated with migrating from staging to maven central. The link from the Spec. page is:
https://search.maven.org/artifact/jakarta.enterprise.concurrent/jakarta.enterprise.concurrent-api/3.0.0/jar
After clicking that, clicking on the Browse icon the folder seems to show a set of artifacts released from April 26, 2022.
If that is not the right artifact you may need to do something to revert and republish the artifacts -- but please check if these are correct first.
I don't know how mvnrepository.com is refreshed. Is it your experience that this usually happens instantly?
The updates (TCK, SHA, SIG, PUB) for the specification page were not part of the original PR -- they will be fixed in the follow-on PR I created to add the ballot results; which I just merged a few moments ago. You won't see that
refreshed until the Specifications web-site is refreshed -- that doesn't happen immediately. Probably tomorrow would be a good time to check. In the mean time, you could check the current _index.md file in the repository:
https://github.com/jakartaee/specifications/blob/master/concurrency/3.0/_index.md
Since I'm also a member of concurrency committer group, I've gone ahead and accepted and closed the CCR issue for OpenLiberty (noting lazy consensus). I documented this and checked this item off the issue.
I'll leave the Maven promotion and web-site check-list items open for you (or someone aside from me) to verify. As I suggested, maybe tomorrow for the site. Someone more fluent with the mechanics of Maven and maven indices may need
to assist if the Maven promotion is still incorrect. If no one here can help, I'd ask Ivar Grimstad for help and/or a referral.
Cheers,
-- Ed
On 5/12/2022 2:18 PM, Nathan Rauh wrote:
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
_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev
