release candidate 2

NorfairKing · Jun 26, 2021 · 3c9356f · 3c9356f
1 parent 7c87d2b
commit 3c9356f
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 2 deletions.
diff --git a/smos-docs-site/content/pages/development/release-checklist.markdown b/smos-docs-site/content/pages/development/release-checklist.markdown
@@ -17,9 +17,9 @@ When a given commit on the `development` branch is supposedly ready for release,
    If the end-to-end tests don't pass, that means we broke either forward or backward compatibility.
    In that case we revert testing to the previous release commit and start over with the release checklist.
 1. Merge `testing` into `staging`.
-1. Deploy to staging
+1. Deploy to staging.
 1. Wait for end-to-end tests to pass again.
-1. Merge `staging` into `release`
+1. Merge `staging` into `release`.
 1. Run the release script to create the appropriate tags
 1. Make a GitHub release with the contents of the changelog.
 1. Upload the release-zip with static binaries to the artefacts of the GitHub release

diff --git a/smos-docs-site/content/unreleased.markdown b/smos-docs-site/content/unreleased.markdown
@@ -0,0 +1 @@
+
diff --git a/smos-docs-site/content/unreleased.md b/smos-docs-site/content/unreleased.md