v1.11 Release Planning

[artursouza]

Release team

Release lead: @artursouza
Release lead shadow(s): @nyemade-uversky @robertojrojas
Perf test lead: @JoshVanL @robertojrojas
Longhaul test: @halspang
Build manager: @JoshVanL

Read about the Dapr release lifecycle

Milestone dates

Feature definition starts: 21st Feb 2023
Feature definition ends: 14th March 2023
Feature freeze: 10th April 2023
Code freeze (Endgame starts): 24th April 2023 1st May 2023
Release day: 10th May 2023 17th May 2023
Announcement day: 11th May 2023 18th May 2023

Feature proposals that impact multiple repos, that maintainers can use to triage

v1.11 Progress tracking board: https://github.com/orgs/dapr/projects/70

Priorities for this release

• Fundamentals
  • Configuration API as stable: Proposal: Make Configuration API stable #5522
  • 1 AWS and 2 GCP components as stable:
    • AWS S3 binding as Stable components-contrib#2247
    • Certify GCP PubSub as Stable components-contrib#2461
    • Certify GCP FIrestore state as Stable components-contrib#2460
  • Validate binary size and virtual memory usage for sidecar: Validate Dapr's sidecar memory and size #6066 (DONE)
  • Validate number of go routines for sidecar: Validate number of go-routines in dapr sidecar #6067 (DONE)
  • Do not install Dashboard by default: remove Dashboard from dapr/dapr's Helm chart and create a new dedicated chart: Proposal: Remove Dashboard from Dapr's Helm Chart #4724 (IN PROGRESS)
  • Multiple flavors of images for Dapr sidecar, starting with "everything" and "just stable components": Offer multiple flavors of Dapr sidecar #3168
  • Port existing longhaul tests (nightly and release) to external Azure subscription: Move longhaul to the same Azure subscription we use for E2E tests test-infra#167
  • Metrics for Actor timers and reminders: Emit metrics for Actor reminder and timer #6032
  • New API in placement service to retrieve placement table: API to retrieve placement table from placement service #6033
  • [STRETCH] Improve mTLS certificate rotation: [PROPOSAL] Identity Management Overhaul #5756
    • To have one root CA instead of 3.
    • Improving how sentry authenticates sidecars
    • Control plane services request their own SPIFFE Id
  • [STRETCH] Support cert manager to own root CA in addition to self-signed: [Proposal] Support third-party CA - Integrate Cert Manager with Dapr #3968
  • Support minTLS configuration: Support Min TLS Version via Configuration #6031~
  • [STRETCH] Allow automatic root CA rotation: [Proposal] Automatic root certificate rotation #5958
  • [EPIC] Create Dapr specific error codes in gRPC and HTTP APIs: Dapr-specific error codes in APIs #6068
  • [STRETCH] Replace FastHTTP with Chi to support streaming and other use cases (HTTP/2.0, etc):Migrate HTTP server from fasthttp to net/http #4979
• [STRETCH] User-(easily)-reproducible performance benchmarks (DOCS/Readme)
• External service-to-service invocation: Proposal: Extend service invocation to non-Dapr endpoints #4549
• [STRETCH] Component hot-reload: Hot reloading of components #1172
• [EPIC] Resiliency not to duplicate retries with components' built-in retries ("component resiliency")
• Workflow improvements
  • Workflow 1.11 Tracking Issue #6111
  • Workflow built-in component must not duplicate retries when resiliency policy is used
• Scale actor reminders registration (improves workflow performance) Incremental improvements to Actor Reminders subsystem #6121
• Crypto(graphy) (not currency) API: [Tracking issue] Crypto(graphy) building block #6147
• Re-design of state store encryption: Dapr state store encryption should switch to AES-CBC #6027
• [STRETCH] Dynamic subscriptions for pubsub
• [CLI] Multi app run (better logging, other improvements): Proposal: consider sending merged STOUT on dapr run -f cli#1238
• [EPIC] SDKs to allow TLS configuration for remote Dapr API: Support configuration for SDKs to talk to remote Dapr APIs #6035
• [Contrib] Refactor metadata parsing to allow metadata spec YAML to be validated and up to date (DONE)
• [STRETCH] [Discussion] Use SQLite as default state store for local development because Redis is not actually transactional (hence should not be used as actor state store)
  • Should we deprecate transaction / actor state store support for Redis?
  • See Is Redis actually transactional? components-contrib#2071

Repo milestones

Dapr - https://github.com/dapr/dapr/milestone/18
CLI - https://github.com/dapr/cli/milestone/12
Docs - https://github.com/dapr/docs/milestone/14
Components-contrib - https://github.com/dapr/components-contrib/milestone/12
Java-SDK - https://github.com/dapr/java-sdk/milestone/9
Python-SDK - https://github.com/dapr/python-sdk/milestone/10
Dotnet-SDK - https://github.com/dapr/dotnet-sdk/milestone/16
Js-SDK - https://github.com/dapr/js-sdk/milestone/12
Go-SDK - https://github.com/dapr/go-sdk/milestone/8
Dashboard: - NOT TO BE RELEASED
Quickstarts (aka Tutorials) - https://github.com/dapr/quickstarts/milestone/7

[mukundansundar]

@dapr/maintainers-dapr This ideally needs to be resolved to some extent before release #6265

[yaron2]

@dapr/maintainers-dapr This ideally needs to be resolved to some extent before release #6265

Agree, triaged to 1.11

[mukundansundar]

@artursouza can this be closed?

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[dapr-bot]

This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.