-
Notifications
You must be signed in to change notification settings - Fork 1
Add more details in the release strategy guide #86
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
base: main
Are you sure you want to change the base?
Conversation
| $ # 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++ in a regular pull request
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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]>
10ec265 to
4dcd33c
Compare
Signed-off-by: Olivier Perrin <[email protected]>
|
TODO: Change the corrective release section to use a PR instead of merging directly in the |
Signed-off-by: Olivier Perrin <[email protected]>
|
TODO: Add collapsing sections dedicated to:
This way, the maintainer can only see the section they need. Since both sections are now very similar, but with differences, it could be misleading to have them both displayed at the same time. |
Signed-off-by: Olivier Perrin <[email protected]>
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