Re: [jakarta.ee-spec.committee] Changes for TCK certification request

[Scott Stark <sstark@xxxxxxxxxx>]

So the update would be to say:

Create a certification request as described in the [https://... TCK Process]. This entails creating an issue in the specification project TCK issue tracker. If there is no TCK repository for a project, use the issues in the repository where the specification document resides.

Should I list the https://github.com/eclipse-ee4j/jakartaee-tck/issues project as the location for the CTS and many standalone TCKs?

On Jul 24, 2019, at 2:50 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

That still ends up being a bit ambiguous as every repo associated with the spec project has an issue tracker. Our spec projects have 1-3 repositories as some have only an api/spec combined, some have a separate TCK repo and some have all three repos separated.

I think we were anticipating the future where there would be separate TCK repositories in each spec project, and the certification requests would be filed in those repositories' issue trackers.

In the mean time, we need to decide what to do.  If the specification project doesn't have a TCK repository, using the issue tracker of the repository containing the specification document is probably best.