Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authorization 3.0 plan #622

Merged
merged 1 commit into from
Jul 12, 2023
Merged

Conversation

arjantijms
Copy link
Contributor

Specification PR template

When creating a specification project release review, create PRs with the content defined as follows.

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:
  • The URL of the staging directory on downloads.eclipse.org for the proposed EFTL TCK binary:
  • The URL of the compatibility certification request issue:
  • 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.

Signed-off-by: Arjan Tijms <arjan.tijms@omnifish.ee>
@ivargrimstad ivargrimstad added the plan review Use this label on PRs that are filed for plan reviews label May 30, 2023
@netlify
Copy link

netlify bot commented May 30, 2023

Deploy Preview for jakartaee-specifications ready!

Name Link
🔨 Latest commit 6e1e44c
🔍 Latest deploy log https://app.netlify.com/sites/jakartaee-specifications/deploys/64760eb9b89a8c000826b18e
😎 Deploy Preview https://deploy-preview-622--jakartaee-specifications.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@Emily-Jiang Emily-Jiang added the ballot Delivered to the Specification Committee for ballot label Jul 4, 2023
@Emily-Jiang Emily-Jiang added the approved The ballot was approved by the Specification Committee label Jul 11, 2023
@Emily-Jiang Emily-Jiang merged commit 60ecad6 into jakartaee:master Jul 12, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved The ballot was approved by the Specification Committee ballot Delivered to the Specification Committee for ballot plan review Use this label on PRs that are filed for plan reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants