Skip to content

Commit 7621f0d

Browse files
authored
Update dev docs patch release workflow (#20875)
1 parent c12971a commit 7621f0d

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

dev_docs/RELEASES.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,16 +10,14 @@ This documentation is for 9.x releases. If you are releasing a 8.x look [here](.
1010
2. Ensure all relevant backport PRs are merged. We use backport labels on PRs and automation to ensure labels are set.
1111
3. Run the [`run-patch-release`](https://github.com/elastic/apm-server/actions/workflows/run-patch-release.yml) workflow
1212
- In "Use workflow from", select `main` branch.
13-
- Then in "The version", specify the **upcoming** patch release version - es: on `8.14.2` feature freeze you will use `8.14.2`).
13+
- Then in "The version", specify the **upcoming** patch release version, e.g.: on `9.3.2` feature freeze you will use `9.3.2`).
1414
- This workflow will:
1515
- Create the `update-<VERSION>` branch.
1616
- Update version constants across the codebase and create a PR targeting the release branch.
1717
4. Release notes for patch releases **must be manually added** at least one day before release.
18-
5. Create a PR targeting the `main` branch and add the backport label for the release branch. To add release notes:
19-
- Add a new section to the existing release notes file ([Sample PR](https://github.com/elastic/apm-server/pull/12680)).
20-
- Review the [changelogs/head](https://github.com/elastic/apm-server/tree/main/changelogs/head.asciidoc) file and move relevant changelog entries from `head.asciidoc` to `release_version.asciidoc` if the change is backported to release_version. If changes do not apply to the version being released, keep them in the `head.asciidoc` file.
21-
- Review the commits in the release to ensure all changes are reflected in the release notes. Check for backported changes without release notes in `release_version.asciidoc`.
22-
- Add your PR to the documentation release issue in the [`elastic/dev`](https://github.com/elastic/dev/issues?q=is%3Aissue%20state%3Aopen%20label%3Adocs) repo ([Sample Issue](https://github.com/elastic/dev/issues/2485)).
18+
5. Create a PR targeting the `main` branch. To add release notes:
19+
- Add a new section to the existing release notes file ([Sample PR](https://github.com/elastic/apm-server/pull/20723)) containing the `Features and enchancements` as well as the `Fixes` subsections.
20+
- Add your PR to the documentation release issue in the [`elastic/dev`](https://github.com/elastic/dev/issues?q=is%3Aissue%20state%3Aopen%20label%3Adocs) repo ([Sample Issue](https://github.com/elastic/dev/issues/3467)).
2321
- The PR should be merged the day before release.
2422

2523
## Minor Release

0 commit comments

Comments
 (0)