[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-tck-dev] Branching and maintenance
|
On 5/14/20 10:55 AM, Ed Bratt wrote:
There has recently been some discussion in a recent PR about the 8.0
branch in the TCK repository. I don't intend this to be commentary on
that specific thread however ...
I just want to put in my vote that we really need a maintenance plan
(branching, release maintenance, etc.) for 8.x. We will need the same
for releases going forward. Our experience is that vendors continue to
require/discover maintenance issues on these releases long after they
are finalized. (Years, maybe even decades. That is life-times in the
life of many projects.)
So, I would urge that a plan needs to be in place and it probably ought
to be documented in a well known location so there isn't confusion about
it and there is the best probability of long term continuity. Please
consider the this so the prospective maintainers, years from now, will
know what to do when they come across those issues and want to apply
their fix.
We do need to document the branching and maintenance plan still.
We have not yet needed to branch our last 8.0 Platform TCK release 8.0.2
but I am thinking that we do need to soon branch the 9.0.0 final release
tag (yet to be created) so that we can use that to release the 5.0.1
Servlet TCK after Jakarta EE 9 is released as final and any other 9.0.*
Platform TCK releases that we need to do.
I suggest that we base the branch name on the Full Platform TCK version
(major.minor):
Jakarta EE version Platform TCK version Branch Name
------------------ -------------------- ---------------
8 8.0.0, 8.0.1, ... 8.0
9 9.0.0, 9.0.1, ... 9.0
9.1 9.1.0, 9.1.1, ... 9.1
...
Make sense?
Scott
Thanks,
-- Ed
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
