After a specifications is approved, a Specification Committee member
will add this checklist to the Pull Request for the specification:
- The
designated specification committee representative adds this
final checklist to the main PR.
- The
specification committee representative merges the specification
PRs.
- The
designated specification committee representative calculates the
staged EFTL TCK signature and promotes it to the committee
download area
using the https://ci.eclipse.org/jakartaee-spec-committee/job/promote-release/
job.
- The
specification project member who created the staging release
promotes the specification api jars to maven central. An example
release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
- The EMO
updates the specification page with the ballot results.
This list goes on the committed spec index page.
- The
specification project team should go through the merged spec
website page to verify all the links are valid.
- The
specification project team should approve the compatibility
request.
- The
compatible implementation project/vendor MUST send an email tck@xxxxxxxxxxx for approval
of the compatible implementation for trademark usage.
- The
specification project team should merge any final release branch
as appropriate for the branch management for the project.
Note that several of the items must be done by members of the
specification project team. That means you!
Whoever submitted the Pull Request should be notified when the
checklist is added. At that point you need to make sure the
project team activities are completed and checked off in the
checklist.
Let me know if you have any questions.
Thanks.