You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
List any special concerns for this release that are not already tracked in another issue, such as release dependencies, Javadoc updates, support level changes, planned docs refresh, etc.
Stabilize and document javadoc publishing procedure
Release checklist
If any Jakarta or MicroProfile API docs are updated with this release, work with development to get the updates merged to the docs-javadoc repo (1-2 weeks before GA)
All issues with a label for this release and any other issues included in the release milestone are completed and closed, with content merged to vNext. (~3 working days before GA)
All autogenerated documentation is refreshed on draft (~3 working days before GA)
Confirm with the team that docs are frozen and no more updates will be sent to vNext (3 working days before GA).
Verify main feature epic statuses to ensure that all targeted features will be included in the release (before closing doc feature issues and again 1-2 working days before GA).
Determine if a docs refresh will be needed before the next upcoming release. If so, make a note of the date and leave this issue open until complete. If not, close this issue.
The text was updated successfully, but these errors were encountered:
Dates
Notes
List any special concerns for this release that are not already tracked in another issue, such as release dependencies, Javadoc updates, support level changes, planned docs refresh, etc.
Stabilize and document javadoc publishing procedure
Release checklist
docs-javadoc
repo (1-2 weeks before GA)The text was updated successfully, but these errors were encountered: