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

24.0.0.6 release #7389

Closed
9 tasks done
dmuelle opened this issue Jun 11, 2024 · 0 comments
Closed
9 tasks done

24.0.0.6 release #7389

dmuelle opened this issue Jun 11, 2024 · 0 comments

Comments

@dmuelle
Copy link
Member

dmuelle commented Jun 11, 2024

This issue tracks the progress of the upcoming Open Liberty release during the release cycle. Name the issue after the release ("x.0.0.x release") and add the appropriate version label.

Dates

  • Doc freeze date: 6.12
  • Estimnated GA Date: 6.18

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.

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)
  • Liberty API/SPI documentation is updated in the docs-javadoc repo and verified on staging site. (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).
  • Publish docs to production on GA
  • If this is a December release, contact the Open LIberty website team to plan for copyright date updates in the January release.
  • 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant