| [jpa-dev] Could one of the committers please add the `challenge` label to persistence/issues/388 and consider accepting it |
Hi,
Could one of the committers add the challenge label to issues/388
[1]. Lukas, please consider accepting the challenge with the
`accepted` label.
FYI the TCK challenge process [4] describes how challenges can be resolved:
"
Challenges can be resolved by a specification project lead, or a
project
challenge triage team, after a consensus of the specification
project
committers is reached or attempts to gain consensus fails.
Specification
projects may exercise lazy consensus, voting or any practice that
follows the principles of Eclipse
Foundation Development
Process.
"
If the challenge is accepted and the proposed fix is approved
[2], we should consider back porting the fix to the Persistence
3.1 + Jakarta EE 10 releases via the [3] 10.0.x branch (which is
where we maintain both TCKs currently). The alternative to fixing
the problem for Persistence 3.1 + EE 10, would be to exclude the
two challenged tests. Lukas, please let me know which path is to
be taken (e.g. accepted with exclude of the tests or accepted with
fix of tests for 3.1 or something else).
Scott
[1] https://github.com/jakartaee/persistence/issues/388
[2] https://github.com/jakartaee/platform-tck/pull/1151
[3] https://github.com/jakartaee/platform-tck/tree/10.0.x
[4] https://jakarta.ee/committees/specification/tckprocess/