Skip to content

WIP release notes for 10.2#3306

Draft
sspencerwire wants to merge 2 commits into
rocky-linux:mainfrom
sspencerwire:WIP_10_2_release
Draft

WIP release notes for 10.2#3306
sspencerwire wants to merge 2 commits into
rocky-linux:mainfrom
sspencerwire:WIP_10_2_release

Conversation

@sspencerwire
Copy link
Copy Markdown
Contributor

@sspencerwire sspencerwire commented May 21, 2026

Author checklist (Completed by original Author)

  • Good fit for the Rocky Linux project? Title and Author Metatags inserted ?
  • If applicable, steps and instructions have been tested to work
  • Initial self-review to fix basic typos and grammar completed

Rocky Documentation checklist (Completed by Rocky team)

  • 1st Pass (Document is good fit for project and author checklist completed)
  • 2nd Pass (Technical Review - check for technical correctness)
  • 3rd Pass (Detailed Editorial Review and Peer Review)
  • Final approval (Final Review)

* add a note that if a package is not listed as noteworthy in the 10.2 release, the differences between that package and previous 10.x packages is probably negligible. Linked to the 10.0 and 10.1 release notes for those migrating to version 10 for the first time.
* remove any sections not covered with a major change in 10.2
* add to sections as needed
* update links
* remove "Current" from the meta for the release notes for 10.1
@sspencerwire sspencerwire marked this pull request as draft May 21, 2026 14:55
@sspencerwire sspencerwire changed the title Wip 10 2 release WIP release notes for 10.2 May 21, 2026
@sspencerwire
Copy link
Copy Markdown
Contributor Author

Please note that the sections for supported architecture and RISC-V, came directly from the 10.1 release untouched. If these need modification, please let me know OR push a fix to the doc. Thanks!

@sspencerwire
Copy link
Copy Markdown
Contributor Author

NOTE: This PR requires the addition of an updated .pages file. It is not included in the PR, because we never know if the minor version of 9 or the minor version of 10 will release first. I may issue two separate PRs for this, with the idea that one will be closed without merging depending on the minor release order of release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant