v1.8 Endgame

[pravinpushkar]

Release Coordinator: @pravinpushkar
Release Buddy: @amulyavarote
Build and Test Champion: @pravinpushkar

Preflight check: 06/14/2022
Code freeze: 06/21/2022
Endgame starts: 06/22/2022
RC1 date: 06/22/2022 (earliest)
Release date: 07/07/2022

Release Tasks:

• No P0 issues before code freeze.
• Code freeze at 06/21/2022
• Check all new components are registered in dapr/dapr @berndverst
• E2E, certification and perf tests are passing @pravinpushkar
• Update components-contrib certification tests go.mods with dapr/dapr 1.8.0-rc.1 commit hash @berndverst
• Create release-1.8 branch and cut RC 1.8.0-rc.1 for component-contrib @berndverst
• Update dapr/component-contrib pkg to 1.8.0-rc.1 in dapr/dapr master branch @berndverst
• Create release-1.8 branch for Dapr runtime @pravinpushkar
• Verify helm chart and cut the 1.8.0-rc.1 release for Dapr runtime @pravinpushkar
• Create release-1.8 branch for CLI @mukundansundar
• Update dapr/dapr pkg to 1.8.0-rc.1 in dapr/cli release-1.8 branch @mukundansundar
• Cut the 1.8.0-rc.1 release for CLI @pravinpushkar
• Notify users about dapr/dapr 1.8.0-rc.1 via Discord, ML @pravinpushkar
• Validate the upgrade path from the previous release -- CRDs updated, no deletion of components/configs etc. ().(This can partially be accomplished by updating the CLI upgrade_test.go) @pravinpushkar
• Validate dapr init in self hosted mode for RC from GHCR and default registry @pravinpushkar
• Validate dapr init in k8s mode for RC from GHCR and default registry @pravinpushkar
• Validate renew-certificate command with a cluster with a Dapr enabled app @pravinpushkar
• Create rc for installer-bundle @shivamkm07
• validate RC for installer bundle @shivamkm07
• Update proto and cut the rc release for Java SDK @artursouza / @mukundansundar
• Update proto and cut the rc release for Python SDK @berndverst
• Update proto and cut the rc release for Go SDK @yaron2
• Update proto and cut the rc release for dontnet SDK @halspang
• Update proto and cut the rc release for cpp SDK @pravinpushkar
• Update proto and cut the rc release for js SDK
• Update proto and cut the rc release for rust SDK @DeepanshuA
• Send dapr runtime/cli to vscode dev containers team @greenie-msft
• Update longhaul tests dotnet SDK version @tanvigour / @halspang
• Update longhaul tests Dapr runtime version @tanvigour / @halspang
• Update tutorials automated validation and check it works - covers Linux Standalone/ K8s / Darwin MacOS. Workflow pulls the latest dapr version before the validations begin @rabollin / @greenie-msft
• Test and validate tutorials in Linux ARM64 k8s and self-hosted @johnewart
• Test and validate tutorials in windows @addjuarez
• Validate Dapr CLI in windows @DeepanshuA
• Validate longhaul metrics @tanvigour / @halspang
• Test and validate the .NET SDK - run through samples @halspang
• Test and validate the java SDK - run through samples @artursouza / @mukundansundar
• Test and validate the python SDK - run through samples @berndverst
• Test and validate the Go SDK - run through samples @yaron2
• Update certification tests in components-contrib release branch (prior to merge back into master) to use the RC and Go SDK release. @berndverst
• Create release notes - CLI, Dapr, .NET SDK, Java SDK, Python SDK, Go SDK. Check them in release branch before cutting the RC release. @pravinpushkar / @msfussell
• Edit and complete release-notes on HackMD
• Verify no breaking changes section in release notes @pravinpushkar
• Merge release notes into release branch and release dapr @pravinpushkar / @yaron2
• Release CLI 1.8 @mukundansundar
• Release Installer Bundle 1.8 @shivamkm07
• Create release-1.8 branch for tutorials, update version tag in the images, create v1.8.0 tag and update the readme in master @pravinpushkar

---

• For all SDKs, update dapr version and SDK rc version, and check e2e tests
• Release cpp-sdk @pravinpushkar
• Release js-sdk
• Release go-sdk @yaron2
• Release java-sdk @artursouza / @mukundansundar
• Release python-sdk @berndverst
• Release rust-sdk @DeepanshuA
• Release dotnet-sdk and release nuget packages @halspang
• Make sure the release notes are copied into the GitHub release description at https://github.com/dapr/dapr/releases @pravinpushkar
• Create components-contrib release from Tag. Copy components release notes section into the description of the release. @berndverst
• In the dapr/dapr release branch, update DEV_CONTAINER_VERSION_TAG in docker/docker.mk to the next release increment. Update the DEV_CONTAINER_CLI_TAG to the latest CLI release. In the same PR also update .devcontainer/devcontainer.json to refer to the new Dev Container version. @ItalyPaleAle
• Manually trigger the dapr-dev-container workflow on the release branch to publish the new dev container (daprio/dapr-dev). @ItalyPaleAle
• In the dapr/components-contrib release branch, update dapr/components-contrib/.devcontainer/Dockerfile to reference the updated dapr-dev image tag for the new release. @pravinpushkar
• In the dapr/cli release branch, update dapr/cli/.devcontainer/Dockerfile to reference the updated dapr-dev image tag for the new release. @pravinpushkar
• Update certification tests in components-contrib release branch (prior to merge back into master) to use latest runtime and Go SDK release. @berndverst
• Generate new Java docs based on the release version of the Java SDK @mukundansundar
• Update supported versions table in docs @hhunter-ms
• Release blog @hhunter-ms
• Tweet release announcement @greenie-msft
• Discord release announcement @greenie-msft
• Update versions in the E2E tests in CLI to the latest runtime and dashboard versions @mukundansundar
• Merge (NOT SQUASH MERGE/AUTO MERGE) back release-1.8 branch into master for required repos
• Celebrate 🎈

[pravinpushkar]

Kindly mention release blockers here in the comments (if there are any)

[mukundansundar]

Java SDK testing and validation ... dapr/java-sdk#756

[msfussell]

Completed and released