Jakarta JSP 3.1 Plan Review

[markt-asf]

Plan Review PR template

When creating a specification project plan 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)
• 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!

🔨 Explore the source changes: b32ed84

🔍 Inspect the deploy log: https://app.netlify.com/sites/jakartaee-specifications/deploys/60d42e551ba5460007517c9c

😎 Browse the preview: https://deploy-preview-366--jakartaee-specifications.netlify.app

[keilw]

@markt-asf The readme file has both Release Review and Plan Review result table, shouldn't they be commented out for now, and just the plan one, at least that's how Authorization 2.1 or Authentication 3.0 (see #356) looked like.

[keilw]

@kwsutter Or is there a certain freedom to leave those and e.g. fix it with the ballot result? If it's OK like that I would start the ballot tomorrow.

[keilw]

I am starting the ballot but I noticed something strange under https://deploy-preview-366--jakartaee-specifications.netlify.app, the page looks weird, @markt-asf could you have a look at that please, I don't think it directly affects this PR so ballot seems OK but it would be nice to correct the formatting of the preview content.
@kwsutter, @ivargrimstad is it possible that preview was affected by other bad or malformed pages around a month ago?

[kwsutter]

Thanks, @markt-asf! Just a nit update -- should clean this up before we merge.

[kwsutter]

I am starting the ballot but I noticed something strange under https://deploy-preview-366--jakartaee-specifications.netlify.app, the page looks weird, @markt-asf could you have a look at that please, I don't think it directly affects this PR so ballot seems OK but it would be nice to correct the formatting of the preview content.
@kwsutter, @ivargrimstad is it possible that preview was affected by other bad or malformed pages around a month ago?

I agree that the Preview is messed up. Something must have happened during this pre-deploy step. I was still able to traverse the pages and find the material. Although it's not formatted correctly, the data looks good. Looks like just a hiccup with the deployment processing...

[keilw]

@kwsutter @ivargrimstad Merged, is it better to sort out the preview now, or could I still push/merge the ballot result first?