doc: how to add a one-off patch to a point release #3530
Merged
Conversation
This file contains 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
github-actions
bot
added
the
documentation
|
Draft as this will need some input on how to handle testenv.properties which needs to have the new tag to avoid this at the start of the top level pipeline: Slack thread to discuss: https://adoptium.slack.com/archives/C09NW3L2J/p1699880299974419 |
|
Back in draft again pending understanding/documenting/resolving this: |
sxa
force-pushed
the
pointreleases1
branch
2 times, most recently
from
39a7ec7
to
33bc3b5
Compare
Signed-off-by: Stewart X Addison <[email protected]>
Added in note about |
karianna
approved these changes
Nov 13, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We do not currently have any documentation on the process for creating point releases in the adoptium mirror repositories. This adds in the information for a one off patch using a branch from a GA tag. A subsequent PR should create the equivalent doc for covering perpetual floating patches in the codebase.
Preview this change at https://github.com/sxa/temurin-build/blob/pointreleases1/RELEASING.md#summary-on-point-releases