-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated the release checklist (#135)
* Updated release checklist * Updated release script to also push the latest tag * Also updated development guide
- Loading branch information
Showing
4 changed files
with
18 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,21 +1,8 @@ | ||
# Release checklist | ||
|
||
1. Update the referenced tags in the documentation | ||
2. If there were changes to the examples: | ||
1. Build and push the new containers: | ||
1. octopod-web-app-example | ||
2. octopod-helm-example | ||
2. Create a new tag incrementing the integer version number of the tag: | ||
1. Build the updated images | ||
2. Tag it with the new `<integer>` (`docker tag`) | ||
3. Push the new tag (`docker push`) | ||
3. Update docs where the tags are referenced. | ||
3. Merge the `develop` branch into the `staging` branch. | ||
4. CI will automatically update the `latest` tag for both `octo` and `octopod`. Wait for CI to complete. | ||
5. Deploy everything in our private cluser and make sure everything works. | ||
6. Merge the `staging` branch into `master` using **Rebase and Merge**. | ||
7. CI will automatically create a new release in GitHub with _octo CLI_ and update the `latest` tag for both `octo` and `octopod`. Wait for CI to complete. | ||
8. Edit the created release in GitHub to match the version you are releasing. | ||
1. Change the release name to the version being released. | ||
2. Uncheck "This is a pre-release" | ||
9. Push the new release of `octo` and `octopod`. To do this run `./release.sh <version>`. | ||
2. If there were changes to control scripts: | ||
1. _**\<TODO\>**_ | ||
3. [Dispatch the "Build and release" workflow](https://github.com/typeable/octopod/actions/workflows/build.yaml), specifying the version you are releasing: | ||
|
||
![](./img/release_workflow.png) |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.