[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-tck-dev] Release of 8.0.2 platform TCK...
|
Scott Marlow wrote on 1/8/20 11:44 AM:
> Does this mean that for the 8.0.2 TCK release, we should use the 8.0.1
> tag + only the test exclusion but not the other changes that have been
> made since the 8.0.1 tag?
If the other changes are test changes, then yes.
> If yes, should we do some branching now, perhaps:
>
> 1. Rename the current master to be an EE 9 branch (ee4j_9?).
> 2. Create a new master branch to use for the 8.0.2 release, based on
> the 8.0.1 tag.
>
> Then, after the 8.0.2 TCK is released, we can rename branches further
> depending on what works best (e.g. rename ee4j_9 back to master if
> that is better).
I'm not sure what the best strategy is to get from here to there,
but we should end up with master containing the "9.0.0" changes,
and a branch containing the (mostly exclude list) changes for 8.0.x.
The latter could be named 8.0-patch or 8.0-maintenance or even just "8.0",
and there would be tags in it for each of the 8.0.x releases.
> Also, should we keep the current EE 8 Jenkins TCK jobs and create new
> ones for EE 9? Or do we move the current Jenkins jobs forward to EE 9
> and call 8.0.2 the last (Jakarta EE 8) TCK release?
We need to be able to run jobs against both EE 8 and EE 9. Whether that's
best done with multiple jobs or parameterized jobs, I don't know. Romain
may have some input on that.
