Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.15 Endgame #8313

Open
mikeee opened this issue Nov 26, 2024 · 0 comments
Open

v1.15 Endgame #8313

mikeee opened this issue Nov 26, 2024 · 0 comments
Assignees
Milestone

Comments

@mikeee
Copy link
Member

mikeee commented Nov 26, 2024

Release team

Release lead: @mikeee
Release lead shadow(s):
Perf test lead: @cicoyle
Longhaul test: @elena-kolevska
Build manager: @JoshVanL

Read about the Dapr release lifecycle

  • Feature definition starts: 27th August 2024 (27/08/2024)
  • Feature definition ends: 10th September 2024 (10/09/2024)
  • Feature freeze: 29th October 2024 (29/10/2024)
  • Code freeze (Endgame starts ~1-2 weeks stabilization): 26th November 2024 (26/11/2024)
  • RC Release day: 20th January 2025 (20/01/2025)
  • Release day: 27th February 2025 (27/02/2025)
  • Announcement day: 27th February 2025 < - Docs, Samples and Runtime, CLI, Release notes

Release Tasks:


  • Check all new components are registered in dapr/dapr @antontroshin
  • E2E, certification and perf tests are passing @cicoyle
  • Create release-1.15 branch and cut RC 1.15.0-rc.1 for component-contrib
  • Update dapr/component-contrib pkg to 1.15.0-rc.1 in dapr/dapr master branch @JoshVanL
  • Create release-1.15 branch for Dapr runtime
  • Verify helm chart and cut the 1.15.0-rc.1 release for Dapr runtime @artursouza
  • Create release-1.15 branch for CLI @artursouza
  • Update dapr/dapr pkg to 1.15.0-rc.1 in dapr/cli release-1.15 branch @artursouza
  • Cut the 1.15.0-rc.1 release for CLI @artursouza
  • Trigger GitHub actions in dapr/homebrew-tap (GitHub disables Actions after 1mo without commits) @mikeee
  • Notify users about dapr/dapr 1.15.0-rc.1 via Discord @mikeee
  • Validate the upgrade path from the previous release -- CRDs updated, no deletion of components/configs etc. @antontroshin
  • Create RC for installer-bundle @mikeee
  • Validate RC for installer bundle @mikeee
  • Update proto and cut the rc release for Java SDK @dapr/maintainers-java-sdk
  • Update proto for Python SDK @dapr/maintainers-python-sdk
  • Update proto for Go SDK @dapr/maintainers-go-sdk
  • Update proto and cut the rc release for dotnet SDK @dapr/maintainers-dotnet-sdk
  • Update proto cpp SDK
  • Update proto for rust SDK @mikeee
  • Cut the rc release for Dashboard Dashboard has no new commits
  • Update longhaul tests with RC for runtime and dotnet SDK @elena-kolevska
  • Update quickstarts/tutorials automated validation and check it works - covers Linux Standalone/ K8s / Darwin MacOS. @mikeee
  • Create PR for quickstarts to point to RC SDKs/Dev package? if it is available @WhitWaldo
  • Test and validate tutorials in Linux ARM64 k8s and self-hosted @mikeee
  • Test and validate tutorials in Windows @mikeee
  • Validate Dapr CLI non-slim scenarios on Windows @antontroshin
  • Validate Multi app run K8s on Windows @antontroshin
  • Validate longhaul metrics @elena-kolevska
  • Test and validate the .NET SDK - run through samples @dapr/maintainers-dotnet-sdk
  • Test and validate the Java SDK - run through samples @dapr/maintainers-java-sdk
  • Test and validate the Python SDK - run through samples @dapr/maintainers-python-sdk
  • Test and validate the Go SDK - run through samples @dapr/maintainers-go-sdk
  • Test and validate the JS SDK - run through samples @dapr/maintainers-js-sdk
  • Test and validate the Rust SDK - run through samples @mikeee
  • Test and validate Dashboard, local mode and kubernetes hosted @yaron2
  • Update certification tests in components-contrib release branch (prior to merge back into master) to use the RC (and Go SDK RC/release if possible). @yaron2
  • Confirm with maintainers that each repo has milestone set for all relevant issues & PRs, then generate release notes
    • CLI @dapr/maintainers-cli
    • runtime @dapr/maintainers-dapr
    • components-contrib @dapr/maintainers-components-contrib
    • .NET SDK @dapr/maintainers-dotnet-sdk
    • Java SDK @dapr/maintainers-java-sdk
    • JS SDK @WhitWaldo
    • Python SDK @dapr/maintainers-python-sdk
    • Go SDK @dapr/maintainers-go-sdk
    • Rust SDK @mikeee
    • Check all milestones for each repo above are up to date before cutting the release notes. @mikeee
  • Validate FOSSA on each repo
  • Edit and complete release-notes on HackMD (everyone)
  • Verify 1.15 documentation @dapr/maintainers-docs

ETA for all above: ~

RELEASE DAY: 05th February 2025

  • Release Dashboard (v0.15.0)
  • Validate breaking changes section in release notes (everyone)
  • Merge release notes into release branch
  • Cut tag for components-contrib
  • Release Dapr 1.15
  • Release CLI 1.15
  • Validate CLI release locations:
    • Chocolatey
    • Winget
    • Brew
  • Release Installer Bundle 1.15
  • Create blog post
  • Release cpp-sdk (v0.13.0)
  • Release js-sdk (v3.5.0)
  • Release go-sdk (v1.12.0)
  • Release java-sdk (v1.13.0)
  • Release python-sdk (v1.15.0)
  • Release rust-sdk (v0.16.0) @mikeee
  • Release dotnet-sdk and release nuget packages (v1.15.0)
  • Create release-1.15 branch for quickstarts, update version tag in the images, create v1.15.0 tag
  • Create components-contrib release from Tag. Copy components release notes section into the description of the release.
  • Validate DevContainers in following repos
    • dapr/dapr
    • dapr/components-contrib
    • dapr/cli
    • dapr/quickstarts
  • Update certification tests in components-contrib release branch (prior to merge back into master) to use latest runtime and Go SDK release.
  • Generate new Java docs based on the release version of the Java SDK

POST RELEASE DAY

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant