Pilot using release plan for data plane unsupported scenarios (handcrafted & SDKs released by SDK team)

[ladonnaq]

Requirement: Develop and implement Release Plan Adoption Plan for onboarding service partners who have data plane handcrafted SDKs or SDKs that are released by the SDK team.

Experiment : The Arch Board PM will create and use a release plan for the upcoming stable release of the Event Grid Namespace SDKs, which are released by the SDK team on behalf of the Azure Event Grid Service team. Link to the Event Grid Namespace Release Plan - https://aka.ms/sdk-release-planner?release-plan-id=16511fa0-f719-ef11-9f8a-0022480bd0ae

Pilot: SDK PM collaborated with Service teams and SDK engineering in using the release plans for these data plane
scenarios for Event Grid Namespace, Cosmos, Storage, and Search.

Next steps:
Pilot has concluded and we are in process of determining the modified workflows for these scenarios. We are using a Figma Jam Board to collaborate on the task flow for each scenarios. https://www.figma.com/board/WP0IIi6wDuBUPR0PTSV2ii/SDKs-released-by-SDK-team-%26-Handcrafted-Scenarios?node-id=0-1&t=awhy3Q95K3CYBRIP-1

Complete

• Pilot with SDK Team team for SDK releases for fall 2024. Identify upcoming releases for these scenarios and assign SDK PM to collaborate with Service teams and SDK engineering in using the release plans.
• Improve Release Plan Summary to address gaps in data (SDK team contacts, API version, API target release month, ...) - Improve API details section of the Release Plan Summary  #8632
• Add tasks to update CODEOWNERS, done for data plane Codeowner epic - [Release Planner] Add step for validating CODEOWNERS #7351 Will be address in this epic, target end of Jan 2025 - Improvements to the "create a release plan" experience to ensure process adherence, automate decision-making, and enhance data integrity  #6262

In Progress

• (In Progress, target Jan 2025) Optimize docs for SDK pull request (data plane) - Optimize docs for SDK pull request (data plane)  #8178
• (In Progress, target Jan 2025) Add new field named "API target release date" with value as month (similar to SDK) Add new field named "API target release date" with value as month (similar to SDK). #8759 Will be address in this epic, target end of Jan 2025 - Improvements to the "create a release plan" experience to ensure process adherence, automate decision-making, and enhance data integrity  #6262
• (In Progress, target Jan 2025) Ask for API version when user associates pull request Ask for API version when user associates pull request  #8631 Will be address in this epic, target end of Jan 2025 - Improvements to the "create a release plan" experience to ensure process adherence, automate decision-making, and enhance data integrity  #6262
• (In Progress, target Jan 2025 for design & requirements) Customize the workflow based on the release scenario - Customized release plans workflows based on the scenario  #8273.
  Determine how the workflows should be enhanced to better support the handcrafted & SDKs released by SDK team
  scenarios. Link to the Figma Jam Board (revised workflow design in progress) - https://www.figma.com/board/WP0IIi6wDuBUPR0PTSV2ii/SDKs-released-by-SDK-team-%26-Handcrafted-Scenarios?node-id=0-1&t=awhy3Q95K3CYBRIP-1

Not Started

• Allow user to select the SDK version from a drop-down box in the generate SDK step for data plane Allow user to select the SDK version from a drop-down box in the generate SDK step for data plane  #8683
• Explore approaches to improving the in-app guidance on how to use the Release Planner App. For example, first time users are often confused by the Milestone being a hyper-link and are unsure how to access the milestone workflows (power apps).
• PR history cataloging: Explore options for cataloging a history of PRs in the release planner to capture changes over time.
• Ensure that all SDK data needed is in the SDK package and is surfaced to the release plan work item for the dashboard - SDK package work item data for Engagement Experience PowerBI Report  #8628