[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartabatch-dev] Service Release Review for v2.1.1 (addressing TCK challenges) underway
|
Where is the staged 2.1.1 tck zip distribution?
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 (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.
Thanks,
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.
|
|
|
Hi Scott,
Is the 2.1.1 batch-tck officially available?
Cheng
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