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
@maririos - This would be an extension use case. If a product is in scope for APEX and the launch lifecycle is GA, the release should be either a new stable SDK version or a new initial SDK version. We need to start adding all of the other release plane use cases to the release planner in March (so that way we can make sure that the UI and backend implementation is completed so we can support by no later than end of April). Let's track this work as part of that Epic and associated release plane - #5561
When selecting the release plans to create, if the Service is targetting Launch type = GA, the tool should propose:
New Beta release of all ....
New GA Release of all ...
This because even though a service is going GA, there might be a beta SDK release before the SDKs go in GA move
The text was updated successfully, but these errors were encountered:
live1206
changed the title
Service with Launch type GA should have Beta and GA release plans suppestions
Service with Launch type GA should have Beta and GA release plans suggestions
Feb 21, 2023
The apps are currently asking the user to specify the type of SDK they want to work on based on the lifecycle of the product.
With that, this issue is done
@maririos - This would be an extension use case. If a product is in scope for APEX and the launch lifecycle is GA, the release should be either a new stable SDK version or a new initial SDK version. We need to start adding all of the other release plane use cases to the release planner in March (so that way we can make sure that the UI and backend implementation is completed so we can support by no later than end of April). Let's track this work as part of that Epic and associated release plane - #5561
When selecting the release plans to create, if the Service is targetting
Launch type = GA
, the tool should propose:This because even though a service is going GA, there might be a beta SDK release before the SDKs go in GA move
The text was updated successfully, but these errors were encountered: