Overview

It's been roughly a year since we last released Azure native. We want to release a new major version (v3), in order to:

1. bumping all the default API versions to the latest reasonable one (details), and
2. implementing fixes and improvements that are breaking changes.

Key KPIs

1. 0 regressions introduced by this release
2. Closes ~80% of the issues labeled 3.0, i.e., ~17 issues, including all blocking ones
3. Adoption: 100% of net-new azure-native users start on v3 after GA
4. Adoption: TODO% of existing users upgrade to v3 within three months
5. SDK size should be in the ballpark of v2.0.0

Key Stakeholders

Engineers: @danielrbradley and @thomas11

Approvers: @mjeffryes

@pulumi/docs to coordinate and help with docs updates

Marketing for promotion

Key Deliverables

• V2 -> V3 release notes with breaking changes and upgrade instructions
• Official release of V3
• pulumi/examples are updated to v3
• pulumi/templates are updated to v3
• Blog post
• Registry docs for V2 are preserved for some amount of time

References 📔

• Project View
• PR/FAQ
• Design Doc
• Decision Log

Basic Process

1. Start implementing the non-breaking issues that can go into master, especially those that influence the automatic part of the major version upgrade
   • Use the Azure RP API when determining default API versions
   • Do not squeeze API versions of resources when the path differs
2. Create v3 branch
3. In parallel
   • Choose new API versions
     • Run discovery to bump default versions
     • Run schema squeeze to remove older versions which can be safely upgraded.
     • Manually curate version selection
   • Implement epic/project issues