[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[jakartaee-tck-dev] Jakarta Platform TCK branching...
|
We currently have the following Platform TCK branches:
- 9.0.x [1] - was last used for handling Jakarta EE 9 TCK
challenges. I expect to use the 9.1.x [2] branch for any
further EE 9 TCK challenges.
- 9.1.x [2] - should be used for handling Jakarta EE 9.1 TCK
challenges. Could also be used for any future 9.x minor
releases (e.g. to create a 9.2.x branch if that is ever
needed).
- master [3] - should be used for developing our changes for the
next Platform release (e.g. Jakarta EE Platform 10).
Questions:
- Do we need the 9.0.x branch [1] for anything at this point?
If not, I suggest that we archive [4] the 9.0.x branch.
- Is anyone against renaming the `master` branch [3] to
something else like `main`? Any other name suggestions?
- Is anyone against moving (Jakarta EE Platform 10) TCK testing
to somewhere else other than our Platform TCK CI [5] system?
This would simplify the EE development process for the Platform
TCK team and also ensure that no EE implementation is treated as
a reference implementation in the future (as much as possible).
(Future) TCK challenge processing would likely need some changes
for how we validate TCK challenges but that is likely easy
enough to deal with.
Scott
[1] https://github.com/eclipse-ee4j/jakartaee-tck/tree/9.0.x
[2] https://github.com/eclipse-ee4j/jakartaee-tck/tree/9.1.x
[3] https://github.com/eclipse-ee4j/jakartaee-tck (master)
[4] https://github.blog/2017-11-08-archiving-repositories
[5] https://ci.eclipse.org/jakartaee-tck