Prepare to release a Persistence jakarta-persistence-tck-3.2.1.zip release #761
Description
The fix for #637 is merged upstream to the master branch via #755. The upstream master branch also contains the source for the Persistence 3.2 TCK but the https://github.com/jakartaee/persistence/tree/3.2-3.2.0 branch does not contain the TCK source.
I suggest that we use this issue to track the overall effort to release the 3.2.1 TCK but first we should figure out where the 3.2.1 TCK should be developed from.
Questions to answer:
- From a process perspective, when TCK challenges are addressed (e.g. always for a released version) we can choose as a Persistence team whether the challenged tests should be excluded or updated. Excluding is easy but reduces coverage. Updating tests can be harder as if we break existing compatible (e.g. already opened a certification request with the Persistence spec) implementations they can open a new challenge which will call for another change that could be either exclude or update the tests. Question is do we want to take the chance of updating tests or take the simpler path of excluding them?
- What is the name of the branch that we should prepare to release the 3.2.1 TCK from?
Regarding question 2, we could create a new branch from the (master) 35f0d53 commit that represents the 3.2.0 TCK release and we could then maintain that branch specifically for future Persistence 3.2 TCK service releases.
For the Persistence 4.0.0 TCK release, we could develop that on the master branch along with the SPEC + API.