Skip to content

Commit 9596a11

Browse files
authored
Merge pull request #946 from buildkite/eleanorkh/update-release-notes
Update release notes
2 parents 350bc96 + 9392d4e commit 9596a11

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

RELEASE.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,15 @@ usually Added, Changed, Fixed, Removed
1111
1. Commit the changelog (don’t use [skip CI] in the commit message, that will prevent the tag from kicking off a build)
1212
1. Push the branch
1313
1. While waiting for the branch to build, test and deploy...
14-
1. Draft a release in GitHub
14+
1. Draft a [release](https://github.com/buildkite/elastic-ci-stack-for-aws/releases) in GitHub
1515
1. Fill in the release version as a git tag, use the release branch as a tag target
1616
1. Set the release title to the the release version
17-
1. Add upgrade instructions to the end of the GitHub release (copied and updated from the previous one)
17+
1. Add upgrade instructions to the end of the GitHub release (copied and updated from the previous one) and update the version numbers in the links.
1818
1. Save the release as a draft (doesn't create the tag until the release is published)
1919
1. Once the branch build has passed, deploy the stack and perform manual of
2020
changed aspects. Once you are satisfied the changes are good and there aren't any
21-
regressions, publish the draft GitHub release to create the tag and kick off the tag build process.
22-
1. Merge the release branch to the repository’s default branch
21+
regressions, publish the draft GitHub release to create the tag and kick off the tag build process, which builds in the Buildkite AWS Stack pipeline.
22+
1. Once the tag is building, merge the release branch to the repository’s default branch
2323
1. Update buildkite/docs with the versions of installed software
2424

2525
## Announcements

0 commit comments

Comments
 (0)