You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASING.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,10 +15,10 @@ as the last step, which publishes a snapshot build to
15
15
* Close the release milestone if there is one.
16
16
* Merge a pull request to `main` updating the `CHANGELOG.md`.
17
17
* The heading for the release should include the release version but not the release date, e.g.
18
-
`## Version 1.9.0 (unreleased)`.
18
+
`## Version 1.9.0 (unreleased)`.
19
19
* Use `.github/scripts/draft-change-log-entries.sh` as a starting point for writing the change
20
20
log.
21
-
* Run the [Prepare release branch workflow](.github/workflows/prepare-release-branch.yml).
21
+
* Run the [Prepare release branch workflow](https://github.com/open-telemetry/opentelemetry-java-contrib/actions/workflows/prepare-release-branch.yml).
22
22
* Review and merge the two pull requests that it creates
23
23
(one is targeted to the release branch and one is targeted to the `main` branch).
24
24
@@ -29,22 +29,22 @@ All patch releases should include only bug-fixes, and must avoid adding/modifyin
29
29
In general, patch releases are only made for regressions, memory leaks and deadlocks.
30
30
31
31
* Backport pull request(s) to the release branch.
32
-
* Run the [Backport workflow](.github/workflows/backport.yml).
32
+
* Run the [Backport workflow](https://github.com/open-telemetry/opentelemetry-java-contrib/actions/workflows/backport.yml).
33
33
* Press the "Run workflow" button, then select the release branch from the dropdown list,
34
34
e.g. `release/v1.9.x`, then enter the pull request number that you want to backport,
35
35
then click the "Run workflow" button below that.
36
36
* Review and merge the backport pull request that it generates.
37
37
* Merge a pull request to the release branch updating the `CHANGELOG.md`.
38
38
* The heading for the release should include the release version but not the release date, e.g.
39
-
`## Version 1.9.0 (unreleased)`.
40
-
* Run the [Prepare patch release workflow](.github/workflows/prepare-patch-release.yml).
39
+
`## Version 1.9.0 (unreleased)`.
40
+
* Run the [Prepare patch release workflow](https://github.com/open-telemetry/opentelemetry-java-contrib/actions/workflows/prepare-patch-release.yml).
41
41
* Press the "Run workflow" button, then select the release branch from the dropdown list,
42
42
e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
43
43
* Review and merge the pull request that it creates.
44
44
45
45
## Making the release
46
46
47
-
Run the [Release workflow](.github/workflows/release.yml).
47
+
Run the [Release workflow](https://github.com/open-telemetry/opentelemetry-java-contrib/actions/workflows/release.yml).
48
48
49
49
* Press the "Run workflow" button, then select the release branch from the dropdown list,
50
50
e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
@@ -55,7 +55,7 @@ Run the [Release workflow](.github/workflows/release.yml).
55
55
56
56
## After the release
57
57
58
-
Run the [Merge change log to main workflow](.github/workflows/merge-change-log-to-main.yml).
58
+
Run the [Merge change log to main workflow](https://github.com/open-telemetry/opentelemetry-java-contrib/actions/workflows/merge-change-log-to-main.yml).
59
59
60
60
* Press the "Run workflow" button, then select the release branch from the dropdown list,
61
61
e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
0 commit comments