Re: [jakartaee-platform-dev] : Re: Pushing RCx or Mx to maven central

[Romain Manni-Bucau <rmannibucau@xxxxxxxxx>]

@Nathan: certification is against signatures, not the binaries so this is a detail point and clearly is not (must not if you look more deeply ;)) be a blocker for any vendor, so all good :).

Romain Manni-Bucau
@rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book

Le jeu. 13 janv. 2022 à 17:39, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> a écrit :

On 2022-01-13 11:35 a.m., Nathan Rauh wrote:

I hope you are not suggesting that compatible implementations certify on a forked copy of the API rather than the official Release Candidate or Milestone artifact.  That does not sound like a legitimate certification.

At the risk of stating the obvious, even an "official Release Candidate or Milestone" does not provide a "legitimate certification". Compatibility claims can only be made based on released binaries under the Eclipse Foundation TCK License.

Of course we all hope that much testing happens using release candidates and milestones :)

---

This email has been checked for viruses by Avast antivirus software. www.avast.com

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev