Cheng,
Sure. Thanks for the note of appreciation.
I didn’t mean to try too hard to gain sympathy there :) just giving a feel for where we were with the processes and automation.
I guess the more we go through with this the more chances to pin down the process.
And thank you too for your help with this release.
Scott
From: jakartabatch-dev <jakartabatch-dev-bounces@xxxxxxxxxxx>
On Behalf Of Cheng Fang
Sent: Thursday, June 23, 2022 12:28 PM
To: jakartabatch developer discussions <jakartabatch-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakartabatch-dev] Service Release Review for v2.1.1 (addressing TCK challenges) underway
Scott, Thanks for getting the release out. Cheng On Jun 23, 2022, at 12:10 PM, Scott Kurz <skurz@xxxxxxxxxx>
wrote: Cheng, I’m sorry for the delay. I’d intended to reply “it’s done” but kept getting distracted.
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
Scott,
Thanks for getting the release out.
Cheng
I’m sorry for the delay. I’d intended to reply “it’s done” but kept getting distracted.
I just did the Maven release and it should sync up in the next couple hours:
To elaborate a bit on my “excuse”:
The Jakarta processes are still new enough that before doing just about anything “release”-related I have to read the process material and talk myself through the fact that I’m doing the correct and necessary
steps. It’s not yet at the phase where there’s a simple checklist. Plus we’re still encountering “new” cases…e.g. if this case we had to do a 2.1.1 service release of both the API JAR and the TCK, but NOT of the spec itself.
That all said, in this case we’d already gone through the process of publishing the 2.1.1 TCK to the Jakarta Batch 2.1 spec page: https://jakarta.ee/specifications/batch/2.1/
so there was really no reason to hold up releasing to Maven Central, if I’d stopped to consider that.
Any updates? It's currently blocking our testing. On Jun 21, 2022, at 12:10 PM, Cheng Fang <cfang@xxxxxxxxxx>
wrote: Our WildFly CI run of batch TCK failed because the artifact jakarta.batch.arquillian.exec-parent is not available in
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
Any updates? It's currently blocking our testing.
Our WildFly CI run of batch TCK failed because the artifact jakarta.batch.arquillian.exec-parent is not available in official release repo or maven central.
Since batch-tck is not a self-contained distribution, it relies on artifacts from public repo. Can we publish all artifacts needed by batch-tck to official release repo?
Yes, this has now been promoted and the link on the spec page is working.
I did upload the 2.1.1 TCK to:
Hopefully that’s all that’s needed.
Where is the staged 2.1.1 tck zip distribution? On Jun 17, 2022 at 4:23:44 PM, Scott Kurz <skurz@xxxxxxxxxx>
wrote: Cheng, You’ll see the links have been updated at the page you mentioned but the 2.1.1 content is not in the right place
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
Where is the staged 2.1.1 tck zip distribution?
You’ll see the links have been updated at the page you mentioned but the 2.1.1 content is not in the right place (the links don’t work).
I believe someone with permission in the Jakarta spec project needs to run a job to promote this. I will ask separately on the spec ML.
Hi Scott, Is the 2.1.1 batch-tck officially available? I checked https://jakarta.ee/specifications/batch/2.1/ which
still does not have the new batch-tck yet. Thanks, Cheng On Jun 9, 2022, at 2:15 PM, Cheng Fang <
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
Is the 2.1.1 batch-tck officially available?
Thanks, Scott. FYI, I just finished my local testing with a local snapshot build of batch-tck. All passed with jberet standalone, and with WildFly 27 Preview snapshot.
That’s right, I’m changing it to 2.1.1 as I’m releasing it.
If it helps someone to see the actual exact source staged now as v2.1.1. in:
I could push it somewhere, but I think it’s going to merge into master (which is mostly updated) so soon that we don’t necessarily need a new branch.
Just to double check, the next batch tck version will be 2.1.1, not 2.2.0. In the current repo, it's set to 2.2.0-SNAPSHOT, but I suppose you intend to change it to 2.1.1 when releasing it? Maybe
it's time to create a 2.1.x branch, to separate
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
Just to double check, the next batch tck version will be 2.1.1, not 2.2.0.
In the current repo, it's set to 2.2.0-SNAPSHOT, but I suppose you intend to change it to 2.1.1 when releasing it?
Maybe it's time to create a 2.1.x branch, to separate from any other future enhancement in tck 2.2?
Here is the TCK v2.1.1 update to address Cheng’s challenges. Some process questions remain but will address elsewhere e.g. spec committee ML:
_______________________________________________
jakartabatch-dev mailing list
jakartabatch-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartabatch-dev
|