Add RELEASE_NOTES.adoc from 2020#202
Open
peter-lawrey wants to merge 2 commits intodevelopfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change moves the project’s release history out of the README and into a dedicated
RELEASE_NOTES.adocdocument.Why
The README previously contained a short, stale “Changes” list covering only a few old releases. That made upgrade impact and recent release history hard to discover.
What changed
Added
RELEASE_NOTES.adoccovering tagged Java-Thread-Affinity releases from 2020 onwards.Summarised releases by:
Added upgrade highlights for the
3.26/3.27/2026.xlines.Documented unreleased branch activity separately from tagged releases.
Replaced the old README “Changes” list with a link to the new release notes.
Updated old wiki references from the personal repository path to the OpenHFT repository path.
Impact
Documentation-only change.
There is no runtime, API, dependency, or build behaviour change. The main benefit is clearer upgrade guidance and a version-controlled release history for users and maintainers.