Scott Stark wrote on 7/24/19 1:19 PM:
In the TCK Process Guide we say to file an issue in 'specification project’s TCK issue tracker’. So that is a bit ambiguous, but given it is the spec project committers that vote on it, I suppose it really should read ’specification project’s issue tracker’, and the directions would simplify to:
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.
For your second point, you think we need a
templated added to the spec committee repo that outlines the
required content from process guide? Makes sense although
ultimately the spec projects would have a custom certification
request issue type with the template. I’ll look at adding that
to inject-api as an example.
Yes, just templatize the list in the TCK process doc so people can
copy/paste it when creating the certification issue.
|
