Maintainer panel
summary
Panel explains concrete contribution and release mechanics: Dapr ships on a roughly every other month cadence (v1.0 in Feb, at v1.4 now), uses a code freeze and long‑lived release branches, cuts RCs and runs e2e tests on AKS, local simulations, conformance tests and performance benchmarks (service invocation prioritized) and automates quickstarts and SDK releases. Governance has a five‑member steering committee (2 Microsoft, 2 Alibaba, 1 Intel). Roadmap includes jRPC and WASM components to enable multi‑language plugins; GA criteria and SDK/ component work (JS, PHP, Java, .NET, Python; Rust desired) are open for contribution.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:22Welcome
- 1:25Arthur
- 5:30Xavier
- 10:51Release process
- 13:50Open governance
- 16:33Documentation
- 18:46SDKs
- 20:09Roadmap
- 23:49Looking forward
- 25:43External plugins
- 27:15Multilanguage components
- 30:45How to contribute
- 41:00Breaking changes
related talks
25mPanel – The Headless OpenSource Stack
27mMechanics of releasing a large project: Leadership learnings from Kubernetes releases
01h 27mMeet the Maintainers: Discuss Roles and Responsibilities, Areas of Improvements and...
39mCommunity and Contributors Panel
01h 05mClosing Panel
45mOpen Source Contribution Panel
46mCore Panel Q&A
46mBuilding Developer Community One Pull Request at a Time