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: dev_docs/RELEASES.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,16 +10,14 @@ This documentation is for 9.x releases. If you are releasing a 8.x look [here](.
10
10
2. Ensure all relevant backport PRs are merged. We use backport labels on PRs and automation to ensure labels are set.
11
11
3. Run the [`run-patch-release`](https://github.com/elastic/apm-server/actions/workflows/run-patch-release.yml) workflow
12
12
- 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`).
14
14
- This workflow will:
15
15
- Create the `update-<VERSION>` branch.
16
16
- Update version constants across the codebase and create a PR targeting the release branch.
17
17
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)).
0 commit comments