Open ladonnaq opened 9 months ago
Per the Design Team guidance, we should not have screenshots of the Release Planner App in our docs. As an alternative, the release plan page describing the steps in a milestone has been updated to direct to other docs pages for more information on the step. We can also include links to completed examples of release plans in the PPE environment.
Here are examples release plans. I will complete all of them and post links to engineering hub. Blocked by permissions for PPE tables (SDK release milestone namespace). Let engineering know and when resolved will complete task.
Private Preview release plan examples:
Public Preview release plan examples:
GA release plan examples:
TODOs: Update release plans once permissions are fixed in PPE for table related to SDK namespace drop-down box. Private Preview release plan examples:
[ ] https://web.powerapps.com/apps/8ca4408d-6af3-475f-90fe-51b2e43624bb?release-plan-id=29932e15-e70b-ef11-9f8a-000d3a56548f (management plane)
[ ] https://web.powerapps.com/apps/8ca4408d-6af3-475f-90fe-51b2e43624bb?release-plan-id=32f0263d-2cd7-ee11-9078-000d3a56548f (data plane)
Public Preview release plan examples:
[ ] https://web.powerapps.com/apps/8ca4408d-6af3-475f-90fe-51b2e43624bb?release-plan-id=22848181-b384-ee11-8179-000d3a5651e3 (data plane)
[ ] https://web.powerapps.com/apps/8ca4408d-6af3-475f-90fe-51b2e43624bb?release-plan-id=91b24965-43ae-ee11-a569-000d3a5651e3 (management plane)
GA release plan examples:
[ ] https://web.powerapps.com/apps/8ca4408d-6af3-475f-90fe-51b2e43624bb?release-plan-id=548cfc43-e70b-ef11-9f89-6045bdffd8f9 (management plane)
[ ] https://web.powerapps.com/apps/8ca4408d-6af3-475f-90fe-51b2e43624bb?release-plan-id=92313459-c984-ee11-8179-000d3a56548f (data plane)
Request engineering to mark all other release plans as abandoned.
Requirement: Update APEX requirement and release plan docs based on stakeholder and service partner feedback
Topics to be covered in revised docs
Common scenarios highlight progression from Beta to Stable SDKs
Scenario 1: Service is not GA, External Product is not GA. Publish initial Preview API version -> Generate & release Beta SDKs (Preview API version) -> Publish initial Stable API version -> Generate & release Stable SDKs (Stable API version)
Scenario 2: Service is GA, new external Product introducing significant changes to the existing RP & ARM REST APIs. Publish new Preview API version - > Generate & release Beta SDKs (Preview API version) -> Publish new Stable API version -> Generate & release Stable SDKs (Stable API version)
Scenario 3: Service is GA, new product which is NOT introducing significant changes to existing RP and ARM REST APIs. Publish new Preview or Stable API version -> Generate & release Beta SDKs (Preview or Stable API version) -> Publish new Stable API version (if there are changes) -> Generate & release Stable SDKs (Stable API version)
Request from Catalinia based on service partner feedback: @catalinaperalta From: Catalina Peralta [Catalina.Peralta@microsoft.com](mailto:Catalina.Peralta@microsoft.com) Sent: Thursday, January 11, 2024 1:37:59 PM To: Justin Bettencourt [jbettencourt@microsoft.com](mailto:jbettencourt@microsoft.com); Mariana Rios Flores [mariari@microsoft.com](mailto:mariari@microsoft.com); LaDonna Quinn [ladonnaquinn@microsoft.com](mailto:ladonnaquinn@microsoft.com) Cc: Laurent Mazuel [lmazuel@microsoft.com](mailto:lmazuel@microsoft.com) Subject: Release planner feedback
Hi all,
I wanted to reach out with a suggestion that I think will help with Release Planner adoption. I’ve noticed that a few service teams seem to be reluctant to begin working with the release planner and usually their questions are related to what information/commitments will be expected of them once they create one. I think having documentation in engineering hub with a step by step tutorial with screenshots of each of the release plan pages would be helpful since some service partners would like to know beforehand what to expect from the app from start to finish. I have seen the diagram we currently have on the site, but I believe a step-by-step tutorial would be even more intuitive and would show service partners what information the app will request from them. This could additionally be done in a video format if we think that would be easier for some folks to learn how to use the release planner.
Here is a quote I got in email today from the Health Insights team about using the release planner: “Is there a tutorial regarding how to complete/use the planner ?”
It would also be good to emphasize that the app is meant to be used by both PMs and developers since I have found that to also be a point of confusion. Highlighting how this app helps/benefits each team member through the process would be helpful and we can start pointing folks to these specific documentation sections to encourage adoption and improve usage.
Let me know if you have any questions or if I can provide any more information. Thanks, Catalina