Support of additional release planner scenarios

[ladonnaq]

I am creating this epic to track the GitHub issues associated with completion of implementation to support all additional release plan scenarios in the new UI and back-end implementation. I will add links to GitHub issues as they are created.

• APEX extensions - Private Preview, Public Preview, GA (release plans are supported but need to identify in Release Planner App if the release plan is an extension). - Support for extensions for APEX  #7913
• Release Plans that map to Service, not product - Support Service level release plans  #7314 Enable teams to use the tool even if they are not part of Service Tree #7522
• Multi-Product Release Plans - Support Service level release plans  #7314
• non-APEX: TypeSpec and OpenAPI supported but need to identify if the release plan is non-APEX via the Release Planner App - Improvements to the "create a release plan" experience to ensure process adherence, automate decision-making, and enhance data integrity  #6262
• (In Progress, requirements & design targeted for end of Jan 2025) Existing HLC SDKs - Pilot using release plan for data plane unsupported scenarios (handcrafted & SDKs released by SDK team)  #8629
• (In Progress, requirements & design targeted for end of Jan 2025) SDKs that are released by the SDK team on behalf of the Service Partner - Pilot using release plan for data plane unsupported scenarios (handcrafted & SDKs released by SDK team)  #8629
• Existing OpenAPI DPG + convenience layer
• TypeSpec DPG + convenience layer
  etc.
• Maintenance release: hot fixes for SDKs
• Maintenance release: regularly SDK updates like monthly or quarterly refreshes
• Retirement of service or product REST APIs and SDKs
• Deprecation or retirement of older API and SDK versions - Service user can use SDK release planner to plan for service or API version retirement #5559

[maririos]

It is a good list to start with. As we have service team onboarding, we will notice which release plans we are mising

[maririos]

@ladonnaq Looks like #4537 will be covered in this epic. Do you want to consolidate both into this one?

[ladonnaq]

@ladonnaq Looks like #4537 will be covered in this epic. Do you want to consolidate both into this one?

Extensions would span multiple scenarios. This issue is to track all of the scenarios that we need to support. Next step would be to prioritize and figure out what is needed to support. I would expect that most of the scenarios are subset of release plan for a new initial SDK release so it should hopefully not be too difficult.

[maririos]

While this works happens, @ladonnaq has agreed to add documentation on our website on how to work around tooling limitations

[ladonnaq]

While this works happens, @ladonnaq has agreed to add documentation on our website on how to work around tooling limitations
I already did add guidance but if we need to duplicate it or move it let me know. It is here now - https://eng.ms/docs/products/azure-developer-experience/onboard/requirements