| Re: [jakartaee-tck-dev] Coordination of EE 10 TCKs + project tracker... |
I added a few new columns for tracking which TCK link + SHA was last used by the SPEC API team to pass the TCK. I also added the TCK link + SHA that was last built by the Platform TCK. I think that this will help us to better understand what the SPEC API teams have used for testing and how that correlates to what the Platform TCK jobs have produced.
Scott
Speaking of coordination, I was just asked [3] what the best way is to inform the TCK team of updated Jakarta EE 10 SPEC API updates being staged on [4]. As mentioned on [3], we just started a tracking spreadsheet [5] that we can use to try coordinate such things.
Feedback on [3][5] is welcome here.
Scott
[3] https://www.eclipse.org/lists/jakartaee-spec-project-leads/msg00778.html
[4] https://jakarta.oss.sonatype.org/content/repositories/staging/
[5] https://docs.google.com/spreadsheets/d/146JPntf-16sBLuSJDjuuTR8oosz-BfEE1x1TcP9Ode4/edit?usp=sharing
On 10/1/21 3:04 PM, Scott Marlow wrote:
[1] is for tracking Jakarta EE 10 Platform TCK issues and [2] is for tracking Jakarta EE 10 TCK issues across multiple projects.
Should we transfer [1] issues to the [2] project?
One reason for tracking issues at the `eclipse-ee4j` [2] level is that can show issues for multiple SPEC projects, instead of just at the Platform TCK level [1].
Scott
[1] https://github.com/eclipse-ee4j/jakartaee-tck/projects/4
[2] https://github.com/orgs/eclipse-ee4j/projects/22