You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If only management plane is in scope then this would be the email to send. The only change I made was to direct teams to go create release plans (without scheduling an Info meeting or attending onboarding). Self-service is the end goal, so let’s try this out and see how it goes. We will remove the “schedule info meeting” from the management plane only scenario and see if office hours is sufficient. Today I do spend a significant amount of time helping management plane end to end for the new initial SDK scenarios.
Based on the information you provided when onboarding to the Azure SDK team, API details are for this product.
Your onboarding record in Azure DevOps is: Triage - Release Planner Test Product
Next steps
• If your product is in scope for APEX, then you should mark the “Lifecycle: Onboard with the Azure SDK team to determine API/SDK scope, ID = d0ac2647-8e12-4fd6-a7f2-69d9747c86b4”, launch criteria as complete and paste the link to the onboarding record in the requester’s notes. See guidance for submitting evidence for APEX signoffs - APEX launch readiness and signoffs (eng.ms)
• Create a release plan and use it to complete work, ensure all requirements are met, and receive APEX signoff for new Azure REST APIs and SDK versions. What is a release plan? (eng.ms)
• Get familiar with the Azure SDK release process and changes in the APEX signoff process https://aka.ms/azsdkdocs
If you have questions, contact us by posting a question to our teams channel, email, or attending Azure SDK Onboarding office hours posted in our teams channel - https://aka.ms/azsdk/onboarding-channel
Your feedback matters to us, and we’d love to hear more about your experience using the Release Planner. Take a quick 2-minute survey to help us improve. Here is a link to the survey.
Regards
Azure SDK Onboarding PM team
Based on the information you provided when onboarding to the Azure SDK team, API details are unsure or data plane is in scope for this product.
Your onboarding record in Azure DevOps is: Triage - Release Planner Test Product
Next steps
• Attend an Informational meeting with the Azure SDK team. If while you onboarded your team you didn’t get prompt to schedule a meeting, please schedule as soon as possible - Azure SDK informational meeting. During the information meeting we will validate the REST APIs in scope for your product/service, provide overview of the new improvements to our process and tooling, and help you create the appropriate release plan(s).
• If your product is in scope for APEX, then you should mark the “Lifecycle: Onboard with the Azure SDK team to determine API/SDK scope, ID = d0ac2647-8e12-4fd6-a7f2-69d9747c86b4”, launch criteria as complete and paste the link to the onboarding record in the requester’s notes. See guidance for submitting evidence for APEX signoffs - APEX launch readiness and signoffs (eng.ms)
• Get familiar with the Azure SDK release process and changes in the APEX signoff process https://aka.ms/azsdkdocs
If you have questions, contact us by posting a question to our teams channel, email, or attending Azure SDK Onboarding office hours posted in our teams channel - https://aka.ms/azsdk/onboarding-channel.
Your feedback matters to us, and we’d love to hear more about your experience using the Release Planner. Take a quick 2-minute survey to help us improve. Here is a link to the survey.
Regards
Azure SDK Onboarding PM team
The text was updated successfully, but these errors were encountered:
If only management plane is in scope then this would be the email to send. The only change I made was to direct teams to go create release plans (without scheduling an Info meeting or attending onboarding). Self-service is the end goal, so let’s try this out and see how it goes. We will remove the “schedule info meeting” from the management plane only scenario and see if office hours is sufficient. Today I do spend a significant amount of time helping management plane end to end for the new initial SDK scenarios.
Based on the information you provided when onboarding to the Azure SDK team, API details are for this product.
Your onboarding record in Azure DevOps is: Triage - Release Planner Test Product
Next steps
• If your product is in scope for APEX, then you should mark the “Lifecycle: Onboard with the Azure SDK team to determine API/SDK scope, ID = d0ac2647-8e12-4fd6-a7f2-69d9747c86b4”, launch criteria as complete and paste the link to the onboarding record in the requester’s notes. See guidance for submitting evidence for APEX signoffs - APEX launch readiness and signoffs (eng.ms)
• Create a release plan and use it to complete work, ensure all requirements are met, and receive APEX signoff for new Azure REST APIs and SDK versions. What is a release plan? (eng.ms)
• Get familiar with the Azure SDK release process and changes in the APEX signoff process https://aka.ms/azsdkdocs
If you have questions, contact us by posting a question to our teams channel, email, or attending Azure SDK Onboarding office hours posted in our teams channel - https://aka.ms/azsdk/onboarding-channel
Your feedback matters to us, and we’d love to hear more about your experience using the Release Planner. Take a quick 2-minute survey to help us improve. Here is a link to the survey.
Regards
Azure SDK Onboarding PM team
Based on the information you provided when onboarding to the Azure SDK team, API details are unsure or data plane is in scope for this product.
Your onboarding record in Azure DevOps is: Triage - Release Planner Test Product
Next steps
• Attend an Informational meeting with the Azure SDK team. If while you onboarded your team you didn’t get prompt to schedule a meeting, please schedule as soon as possible - Azure SDK informational meeting. During the information meeting we will validate the REST APIs in scope for your product/service, provide overview of the new improvements to our process and tooling, and help you create the appropriate release plan(s).
• If your product is in scope for APEX, then you should mark the “Lifecycle: Onboard with the Azure SDK team to determine API/SDK scope, ID = d0ac2647-8e12-4fd6-a7f2-69d9747c86b4”, launch criteria as complete and paste the link to the onboarding record in the requester’s notes. See guidance for submitting evidence for APEX signoffs - APEX launch readiness and signoffs (eng.ms)
• Get familiar with the Azure SDK release process and changes in the APEX signoff process https://aka.ms/azsdkdocs
If you have questions, contact us by posting a question to our teams channel, email, or attending Azure SDK Onboarding office hours posted in our teams channel - https://aka.ms/azsdk/onboarding-channel.
Your feedback matters to us, and we’d love to hear more about your experience using the Release Planner. Take a quick 2-minute survey to help us improve. Here is a link to the survey.
Regards
Azure SDK Onboarding PM team
The text was updated successfully, but these errors were encountered: