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.
Though we could do one…
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:
