Updates for the 2.2 release of interceptors

[starksm64]

Draft of the Interceptors 2.2 spec update. Needs to wait on the CDI TCK for finalization.

Include the following in the PR:

• A directory in the form wombat/x.y where x.y is the release major.minor version, and the directory contains the following.
• Specification PDF in the form of jakarta-wombat-spec-x.y.pdf
• Specification HTML in the form of jakarta-wombat-spec-x.y.html
• A specification page named _index.md following the template at:
  https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md
• For a Progress Review, that sufficient progress has been made on a Compatible Implementation and TCK, to ensure that the spec is implementable and testable.
• For a Release Review, a summary that a Compatible Implementation is complete, passes the TCK, and that the TCK includes sufficient coverage of the specification. The TCK users guide MUST include the instructions to run the compatible implementations used to validate the release.
  Instructions MAY be by reference.
  • Updated release record
  • Generated IP Log
  • Email to PMC
  • Start release review by emailing EMO
• The URL of the OSSRH staging repository for the api, javadoc:
  https://jakarta.oss.sonatype.org/content/groups/staging/jakarta/interceptor/jakarta.interceptor-api/2.2.0/
• The URL of the staging directory on downloads.eclipse.org for the proposed EFTL TCK binary:
  CDI 4.1 TCK
• The URL of the compatibility certification request issue:
  CDI 4.1 CCR
• Specification JavaDoc in the wombat/x.y/apidocs directory.
  If desired, an optional second PR can be created to contain just the JavaDoc in the apidocs directory.

Note: If any item does not apply, check it and mark N/A below it.

[netlify]

✅ Deploy Preview for jakartaee-specifications ready!

Name	Link
🔨 Latest commit	13e7f2f
🔍 Latest deploy log	https://app.netlify.com/sites/jakartaee-specifications/deploys/660d7927b976a20008b4b859
😎 Deploy Preview	https://deploy-preview-702--jakartaee-specifications.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ivargrimstad]

Are the Interceptor signature tests run by Weld for CDI enough for a CCR for Interceptors?

https://raw.githubusercontent.com/wiki/jakartaredhat/cdi-tck/Jakarta-CDI-4.1-TCK-Weld-Results-17.md
https://raw.githubusercontent.com/wiki/jakartaredhat/cdi-tck/Jakarta-CDI-4.1-TCK-Weld-Results-21.md

[Emily-Jiang]

@starksm64 I reviewed this and have the following 2 comments:

1. change log is missing for this release.
2. Compatible implementation says tbd. I think it should be weld-xxx.

[starksm64]

@Emily-Jiang The change log and CI have been updated.

[Emily-Jiang]

@starksm64 I didn't see the 2.2 change log in the spec doc

[starksm64]

@Emily-Jiang the spec change log has been updated

[kazumura]

The link format of "The URL of the OSSRH staging repository" is incorrect.
Maybe brackets ('[' and ']') are not needed.

[Emily-Jiang]

@starksm64 can you the above comments from @kazumura and @Pandrex247 before you merge this PR

[starksm64]

@Emily-Jiang this has been updated as per the comments and vote comments

[mtdelgadoa]

Hello all,
the EMO is trying to avoid duplication of release records, so we will be providing our feedback and comments related to this release directly here.

Please consider adding a security file to your project repository.

EDP Review status: COMPLETED - Awaiting spec committee ballot

Release record: Jakarta Interceptors™ 2.2 Release Review

EMO review checklist

EF Specification Process

• Spec Committee Ballot completed

Intellectual Property Management

• All project code has copyright and license headers correctly applied. ** EMO will scan the code at their discretion **
• All distributed third-party content has been vetted by the IP Due Diligence process (i.e., IP Log has been approved)

Open Source Rules of Engagement

• PMC approval on the mailing list

General:

• Project is operating within the mission and scope defined in its top-level project’s charter
• Project is operating within the bounds of its own scope
• Project is operating in an open and transparent manner
• Overall the project is operating according to the Eclipse Development Process.

Things to check:

• Communication channels advertised
• Advertised communication channels used
• Committers are responding to questions
• Committers are responding to issues
• Committers are responding to pull/merge/review requests

Branding and Trademarks
The following applies when the project has a custom website.
To the best of our knowledge:

• Project content correctly uses Eclipse Foundation trademarks
• Project content (code and documentation) does not violate trademarks owned by other organizations

Things to check:

• Project website uses the project's formal name in first and all prominent references
• Project website includes a trademark attribution statement
• Project website footers contain all necessary elements

Legal Documentation
Required files:

• License files in all repository roots
• README
• CONTRIBUTING (or equivalent)

Recommended files:

• NOTICES or equivalent (you can use the Legal Documentation generator available under committer tools)
• CODE_OF_CONDUCT
• SECURITY

See examples for Security file and Code of Conduct.

Required elements:

• ECA is referenced/described

Recommended elements:

• Build instructions provided
• Security policy is described

Metadata (PMI)

• The formal name, e.g. "Eclipse Foo™", is used in the project title
• The formal name including appropriate marks (e.g, "™") is used in the first mention in the text of the project description, and scope
• The project description starts with a single paragraph that can serve as an executive summary
• Source code repository references are up-to-date
• Download links and information are up-to-date (see EF handbook for more information on how-to do this)
• Communication channels listed in the PMI (i.e. public mailing list, forums, etc.)

[Emily-Jiang]

• On ballot completion, the specification committee mentor:

• adds this final checklist to the main PR.
• adds the approved label to the PRs, and sends out the Ballot Summary per this template to the public Jakarta EE Specification Committee email list
• 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. Manually editing the jenkins Build Information will help identify the build (ie. Mail 2.0 or CDI 3.0).
• merges the specification (and apidocs) PRs, ensuring the "date:" field in the _index.md file has an appropriate value to allow publishing.
• updates the specification page with the ballot results. This is normally done via a separate PR that should be reviewed, approved, and merged.
• notifies the EMO of the ballot results by email to emo@eclipse-foundation.org. Just forward the ballot summary note sent earlier to the public Spec Committee email list.
• creates an issue in the specification project that includes the following checklist for the specification project team: