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

[Scott Stark <sstark@xxxxxxxxxx>]

If you go to this fork of the injection-api project and start a new issue:

https://github.com/jakartaredhat/injection-api/issues/new/choose

You will see the ‘’ issue type, and clicking that shows the template content.

A PR to add a template file to the spec committee repo is:

https://github.com/jakartaee/specifications/pull/60

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

I'm not sure what you intend with the last sentence.

For all the specs whose TCK is produced from the jakartaee-tck repo, should they use the issue tracker associated with that repo?  Or should they use the issue tracker associated with the repo containing their specification document?

For the PR template, can we add a link to the (to be created) TCK certification issue template?  (We can probably create that template in the specification-committee repo.)

Scott Stark wrote on 7/24/19 12:32 PM:

This is the proposed change to the How_to_Prepare_API_Projects_for_the_Jakarta_EE_8_Release page:

##* Create a certification request as described in the [https://docs.google.com/document/d/1Et3LtK-2SUuAoOV56t8R8fKnRWhbWqg9SLgm-VhbDPY/edit#heading=h.lj6gviz0pbd8 TCK Process]. This entail creating an issue in the specification TCK issue tracker. If a project does not have a separate TCK issue tracker, use the specification project issue tracker.

<WikiPageDiff.png>

The proposed change to the PR template is:

https://github.com/jakartaee/specifications/pull/59

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee