@@ -140,7 +140,9 @@ key to your GitHub account. Once these steps are completed, the commit signing
140140verification will look like the example in GitHub's
141141[GPG Signature Verification feature announcement](https://github.com/blog/2144-gpg-signature-verification).
142142
143- ## Release Cadence
143+ ## Release Information
144+
145+ ### Release Cadence
144146
145147There is no defined release schedule for the bootstrap script at this time.
146148Typically, SaltStack's release team determines when it would be good to release
@@ -154,6 +156,21 @@ Timing the release usually involves an analysis of the following:
154156- Fixes needed for inclusion in an upcoming version of [Salt](https://github.com/saltstack/salt)
155157- Length of time since the last bootstrap release
156158
159+ ### Release Process
160+
161+ The release process consists of the following steps:
162+
163+ 1. Merge in any outstanding PRs that are ready.
164+ 1. Add new contributors to the [AUTHORS](https://github.com/saltstack/salt-bootstrap/blob/develop/AUTHORS.rst) file.
165+ 1. Update the [ChangeLog](https://github.com/saltstack/salt-bootstrap/blob/develop/ChangeLog).
166+ 1. Update the version number in the bootstrap script. The version number is date-based, `<year.month.day>`.
167+ For example, version `2018.08.15` was released on August 15, 2018.
168+ 1. Merge the `develop` branch into the `stable` branch.
169+ 1. Update `bootstrap.saltstack.com` with the new stable release. The checksum on the
170+ [README page](https://github.com/saltstack/salt-bootstrap/blob/develop/README.rst)
171+ should also be updated.
172+ 1. Merge the new stable release into [Salt](https://github.com/saltstack/salt).
173+
157174## Adding Support for Other Operating Systems
158175
159176The following operating systems are detected, but Salt and its dependency
0 commit comments