Plan for Jakarta NoSQL 1.1

[otaviojava]

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.
• An index page wombat/x.y/_index.md following template
• Title should be on the form "Jakarta Wombat X.Y (under development)"
• Includes a plan for the release. Usually, a couple of statements is enough. Otherwise, a link to a document describing the release.
• Includes a detailed description of any backward incompatibility (Mark with N/A and check if none)
• N/A Declares optional features if there are any (Mark with N/A and check if none)
• Includes minimum Java SE version
• Describe any updates or required changes including splitting out the TCK (Mark with N/A and check if not planned)
• Link to updated release record

[netlify]

✅ Deploy Preview for jakartaee-specifications ready!

Name	Link
🔨 Latest commit	9a005aa
🔍 Latest deploy log	https://app.netlify.com/sites/jakartaee-specifications/deploys/68073897a1a24500082ec71e
😎 Deploy Preview	https://deploy-preview-834--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.

[kazumura]

@otaviojava
Could do with the following points being addressed:

• Describing that this release is targeted for Jakarta EE 12.
• How to communicate with the Specification committer team (team list, issue tracker, etc.)
• Brief outline describing how TCK will be developed.
• Name or list of target implementation partners

[otaviojava]

Thanks for the feedback @kazumura could you check it again?