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
Requirement: New initial Beta and new initial Stable SDKs need to be identified in the create a release plan flow by the user as the requirements are different for first initial SDK releases.
Scenario: A service partner has new management plane (ARM) or data plane REST APIs and they plan to release the client and/or management libraries as a new initial SDK package. The new initial SDK packages should be Beta for 30 days minimum before releasing as stable SDKs.
The content you are editing has changed. Please copy your edits and refresh the page.
ladonnaq
changed the title
New initial Beta and new initial Stable SDKs need to be identified in the create a release plan flow
New initial Beta and new initial Stable SDKs need to be identified in the create a release plan flow (Committed for dilithium-2H)
Mar 22, 2024
FYI @maririos - I completed these tasks today since I was updating the release plan work item.
Add new picklist ADO custom field to the release plan work item to identify if release plan is for new initial SDK. The new custom field name = "isInitialSDK" with string picklist values of "yes" or "no". (La Donna)
Add new picklist ADO custom field to release plan work item to identify if the release plan is for a Beta or Stable SDK. The new custom field name = "SDK type to be released" with string picklist values of "beta" or "stable". The current "Create a release plan" UI already ask this question, so all that is needed is for the automation to update this field when a release plan is created.(La Donna)
ladonnaq
changed the title
New initial Beta and new initial Stable SDKs need to be identified in the create a release plan flow (Committed for dilithium-2H)
New initial Beta and new initial Stable SDKs need to be identified in the create a release plan flow
Aug 20, 2024
Requirement: New initial Beta and new initial Stable SDKs need to be identified in the create a release plan flow by the user as the requirements are different for first initial SDK releases.
Scenario: A service partner has new management plane (ARM) or data plane REST APIs and they plan to release the client and/or management libraries as a new initial SDK package. The new initial SDK packages should be Beta for 30 days minimum before releasing as stable SDKs.
Tasks
The text was updated successfully, but these errors were encountered: