Skip to content

Commit

Permalink
chore: add issue reference to dangling commits
Browse files Browse the repository at this point in the history
  • Loading branch information
jakobmoellerdev committed Nov 18, 2024
1 parent 662b007 commit da7adf4
Showing 1 changed file with 9 additions and 2 deletions.
11 changes: 9 additions & 2 deletions RELEASE_PROCESS.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,13 @@ The transformation thus looks like
<major>.<minor>.<patch>-dev -> <major>.<minor>.<patch>-rc.<rc-number>
```

TODO: Currently all releases are created via tag only, so the VERSION bump
that is needed for the release is done through a dangling commit (a commit
that is not part of the history of any branch in the repository). This is not
ideal and should be changed in the future.
See [this issue](https://github.com/open-component-model/ocm/issues/1099)
for details.

### Creating a Minor release

Once a release candidate is seen as sufficiently tested, the release manager can
Expand Down Expand Up @@ -226,8 +233,8 @@ and it will be used for the release.
and thus need a PR to main to append them, or if we want to drop them in the
future. Thats because they are currently needed to correctly manage notes
over multiple release candidates, see
[this issue](https://github.com/open-component-model/ocm/issues/1097) for
details.)
[this issue](https://github.com/open-component-model/ocm/issues/1097)
for details.)

By default, this file is generated from the
appropriate draft release with the basic release name (e.g. `v0.1.0-rc.1.md`).
Expand Down

0 comments on commit da7adf4

Please sign in to comment.