Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jta-dev] Fwd: [jakartaee-spec-project-leads] Handling Certification Requests

As per the message below, please can I ask who of the committers [1] would be willing to perform the verification steps below on https://github.com/eclipse-ee4j/jta-api/issues/50

I don't think I should be the one to do it as I filed the request so it seems contrary to guidance in the mail below.

It's not 100% clear if we should do this now or should coordinate to do this with the other Jakarta projects at some agreed time but it would be useful to know who will be doing it at that time.

Thanks,
Tom

[1] https://projects.eclipse.org/projects/ee4j.jta/who

---------- Forwarded message ---------
From: Ivar Grimstad <ivar.grimstad@xxxxxxxxx>
Date: Wed, 21 Aug 2019 at 07:48
Subject: [jakartaee-spec-project-leads] Handling Certification Requests
To: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>


Hi,

Here is some additional information regarding certification requests. It is the responsibility of the specification project to handle certification requests. Please make sure that your project members are on board with this and comfortable with handling these requests.

The complete documentation can be found in the Jakarta EE TCT Process Document, https://github.com/jakartaee/specification-committee/blob/master/process.adoc#jakarta-ee-tck-process-10.

You must verify that:
- the data is complete
- the number of tests passed is consistent with the first implementation used to validate the TCK
- the TCK version and digital fingerprint match.
- the test results are public and do not require special signup or viewing steps

If your project requires additional requirements for certification requests, you must verify these as well as described in your TCK documentation

In practice:
- Check that the links are correct
- Check that the version numbers are correct
- Check that the version is released. Does not need to be a final release, but cannot be a SNAPSHOT.
- Verify the SHA for the linked files
- Check that everything looks ok and that you are comfortable that the implementation meets your requirements

You don't have to 
- Run the tests
- Verify that the results are accurate or true

Approval
- When the request has been reviewed and approved, close the issue with the label "accepted"
- The one closing the request issue should be someone else than the one that filed it

Hope this helps!

Ivar





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

Back to the top