Steps to finalize the release of Jakarta RESTful Web Services 4.0

ivargrimstad commented 2 months ago

Project Team:

[x] promotes api staging release promotes the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
[x] go through the merged jakarta.ee specification website page to verify all the links are valid.
[x] if XML Schemas are published on https://jakarta.ee/schemas, send a PR to update the status from Draft to Final.
[x] approve the compatibility request.
[x] The compatible implementation project/vendor MUST send an email to tck@eclipse.org for approval of the compatible implementation for trademark usage.
[x] merge any final release branch as appropriate for the branch management for the project.

mkarg commented 2 months ago

Project Team:

* [ ]  The compatible implementation project/vendor MUST send an email to [tck@eclipse.org](mailto:tck@eclipse.org) for approval of the compatible implementation for trademark usage.

How are we, the project team, supposed to fulful this? We are not legitimated to act in the names of all possible vendors of compatible implementations.

jamezp commented 2 months ago

I sent an email for RESTEasy and got an automated response. I suppose that is all that is needed.

ivargrimstad commented 2 months ago

Project Team:
* [ ]  The compatible implementation project/vendor MUST send an email to [tck@eclipse.org](mailto:tck@eclipse.org) for approval of the compatible implementation for trademark usage.
How are we, the project team, supposed to fulful this? We are not legitimated to act in the names of all possible vendors of compatible implementations.

Right, this is a task for the vendor. I guess this is sort of a leftover from the days when there was a single team doing both specs and implementations. I'll see if we can get it removed from this checklist in the future. I also believe that it is of more importance for the products implementing the Platform , Web-, or Core Profile than for individual component specifications.

scottmarlow commented 2 months ago

Right, this is a task for the vendor. I guess this is sort of a leftover from the days when there was a single team doing both specs and implementations. I'll see if we can get it removed from this checklist in the future. I also believe that it is of more importance for the products implementing the Platform , Web-, or Core Profile than for individual component specifications.

Thanks @ivargrimstad, it would be good to better understand if we as a community need the Spec Ballot process to include this step for all EE Specifications.

Step 4 of the https://www.eclipse.org/legal/tck.php page has more details as well on sending the email to tck@eclipse.org for anyone that handles that step:

Before any claim of compatibility (or any similar claim suggesting compatibility) is made based on the TCK, the testing party must:

use the TCK to demonstrate that the Product fully and completely meets and satisfies all requirements of the TCK;

make TCK test results showing full and complete satisfaction of all requirements of the TCK publicly available on the testing party’s website and send a link to such test results to Eclipse at tck@eclipse.org; and

comply with any requirements stated in the Specification with regard to subsetting, supersetting, modifying or extending the Specification in any Product claimed to be compatible with the Specification.

jansupol commented 2 months ago

I have sent the email for the approval for Jersey as well. I never know where the trademark applies, though. Only full Jakarta EE certified products are listed https://jakarta.ee/compatibility/.

ivargrimstad commented 2 months ago

Any estimate of when the API will be released to Maven Central?