Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] [External] : Jakarta Platform TCK branching...

The `9.0.x` branch is now archived (tag was pushed and branch deleted).


We just created https://github.com/eclipse-ee4j/jakartaee-tck/tree/tckrefactor branch for developing the EE 10 TCK changes as a proof of concept.  Starting as soon as next week, we will schedule Platform TCK calls to discuss ideas for refactoring the Platform TCKs.


On 6/30/21 9:56 AM, Scott Marlow wrote:


On 6/30/21 8:25 AM, Gurunandan Rao wrote:
Thanks Scott,
My views on some of the points raised:
  1. We should be able to go ahead with archive of 9.0.X branch.
Thanks
  1. For any new contributors of TCK(and an user of github) 'master' branch is intuitive, are there  advantages with rename of 'master' branch?

The reason to rename the `master` branch is for improving diversity.


Scott


regards,
Guru
From: jakartaee-tck-dev <jakartaee-tck-dev-bounces@xxxxxxxxxxx> on behalf of Scott Marlow <smarlow@xxxxxxxxxx>
Sent: 30 June 2021 03:22
To: jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Subject: [External] : [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:

  1. 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.
  2. Is anyone against renaming the `master` branch [3] to something else like `main`?  Any other name suggestions?
  3. 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


_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev

Back to the top