Skip to content

Conversation

@olperr1
Copy link
Member

@olperr1 olperr1 commented Mar 26, 2025

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • A PR or issue has been opened in all impacted repositories (if any)

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

@olperr1 olperr1 requested review from flo-dup and vidaldid-rte March 26, 2025 10:25
$ # 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.

Copy link
Contributor

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

Copy link
Contributor

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).

@olperr1 olperr1 force-pushed the release_strategy_updates branch from 10ec265 to 4dcd33c Compare April 1, 2025 15:26
@olperr1
Copy link
Member Author

olperr1 commented Jul 18, 2025

TODO: Change the corrective release section to use a PR instead of merging directly in the release-vX.Y.0 branch.

@olperr1 olperr1 marked this pull request as draft October 8, 2025 09:36
Signed-off-by: Olivier Perrin <[email protected]>
@olperr1
Copy link
Member Author

olperr1 commented Oct 8, 2025

TODO: Add collapsing sections dedicated to:

  • a main release
  • a corrective release

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]>
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.

5 participants