v1.0.0 Endgame #194
Description
End game Lead: @yaron2
End game buddy: @artursouza
This is the schedule for the v1.0.0 release
2/10 5:00 PM PST code freeze for the release
- Code freeze at 12:00 pm 2/10
- No P0 issues before code freeze.
- E2E and perf tests are passing. (Known perf test failures, deemed not a blocker. Known E2E failure not a blocker).
- Merge master into release-1.0 branch for component-contrib (@yaron2)
- Cut 1.0.0-rc.5 release for component-contrib (@wcs1only)
- Update component-contrib pkg to 1.0.0-rc5 in dapr/dapr master branch (@yaron2)
- Test and validate latest dashboard RC (@artursouza).
- Update helm chart versions (@yaron2)
- Merge master release-1.0 branches for Dapr runtime (@yaron2 @artursouza )
- Merge master into release-1.0 branch for CLI (@mukundansundar )
- Cut the 1.0.0-rc.4 rc release for Dapr runtime (@yaron2 @artursouza )
- Cut the 1.0.0-rc.5 release for CLI (@mukundansundar )
- Update proto and cut the rc4 release for Java SDK (@artursouza)
- Update proto and cut the rc5 release for .Net SDK (@vinayada1)
- Share RC build. Communicate Dapr uninstall steps to committed customers. Must have new CLI (@yaron2, @artursouza, @msfussell )
- Send dapr runtime/cli to vscode dev containers team (Phil Hoff, @mukundansundar )
2/11 Milestone's date
- Update longhaul tests dotnet SDK version (@wcs1only)
- Update longhaul tests Dapr runtime version (@wcs1only)
- Test Certificate export and Kubernetes upgrade path. (@yaron2)
- Test and validate quickstarts in Darwin (@wcs1only)
- Test and validate quickstarts in Linux k8s (@wcs1only )
- Test and validate quickstarts in Linux self-hosted (@yaron2)
- Test and validate quickstarts in Linux ARM64 k8s and self-hosted (@artursouza )
- Test and validate quickstarts in Windows (@Karishma-Chawla )
- Update proto clients in cpp-sdk (@wcs1only)
- Update proto clients in js-sdk (@tcnghia, PR: Update proto from 1.0.0-RC.3 js-sdk#71)
- Update proto clients in rust-sdk (@tcnghia, PR: Update to 1.0.0-rc.3 protos rust-sdk#37)
- Update proto clients in python-sdk (@wcs1only )
- Test and validate the .NET SDK - run through samples (@vinayada1 )
- Test and validate the .Java SDK release 1.0.0-rc4 - run through integration tests and samples (@artursouza )
- Test and validate the python SDK release - run through samples (@wcs1only)
- Test and validate the Go SDK release - run through samples (@yaron2)
- Create release notes - CLI, Dapr, .NET SDK, Java SDK, Python SDK, Go SDK. Check them in release branch before cutting the RC release. (@yaron2, @artursouza) (Be sure to add breaking changes guide for dotnet, and java SDKs)
2/12
- Release and test azure-function-extensions (@vinayada1)
- Verify breaking changes section in release notes (@halspang)
- Validate Longhaul metrics (@wcs1only)
- Ensure the docs are clear about using the correct CLI version (1.0.0) (@orizohar )
2/16
- Release cpp-sdk (@wcs1only)
- Release js-sdk (@tcnghia )
- Release rust-sdk (@tcnghia )
- Release python SDK (@wcs1only)
- Release Go SDK and docs (@yaron2)
- Release Java SDK and docs (@artursouza )
- Release PHP SDK and docs (@withinboredom )
- Release dotnet SDK and release nuget packages (@vinayada1)
- Create new release for 1.0 branch for docs in the repos (@orizohar, @AaronCrawfis)
- Make v1.0 in docs visible in dropdown (@orizohar, @AaronCrawfis)
- Merge master into release-1.0 branch for quickstarts, update version tag in the images, create v1.0.0 tag and update the readme in master (@wcs1only)
- Make sure the release notes are copied into the github release description at https://github.com/dapr/dapr/releases (@orizohar)
- Release dapr-workflows (@yaron2)
- Generate new Java docs based on the release version of the Java SDK (@artursouza )
- Merge (NOT SQUASH MERGE) back release-1.0 branch into master for required repos (@yaron2 @artursouza)
- Celebrate
RELEASE NOTE: NOT APPLICABLE