Add more details in the release strategy guide #86
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
| $ # You should not have RC or SNAPSHOT versions (except your own repo's one) | ||
| ``` | ||
| If it is not the case, then the bump of the dependencies should be done prior to releasing. | ||
|
|
There was a problem hiding this comment.
++ in a regular pull request
There was a problem hiding this comment.
If the README contains POM examples they should be updated to include the right versions for the project beeing releases and its dependencies (to include in the bump version commit or before so that it is included in the release tag).
Signed-off-by: Olivier Perrin <[email protected]>
Signed-off-by: Olivier Perrin <[email protected]>
olperr1
force-pushed
the
release_strategy_updates
branch
from
10ec265 to
4dcd33c
Compare
flo-dup
approved these changes
Apr 2, 2025
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No
What kind of change does this PR introduce?
Docs update
What is the new behavior (if this is a feature change)?
More detailed release strategy guide