Our current deprecation policy under for stack lifecycle is missing the scenarios if a parent stack falls under a deprecation case but has a child stack/sample which is still being maintained. An investigation should be done to see what process would be best to address these scenarios.
Two ideas I have is to:
Require stack owners of maintained children to migrate content from deprecating parent stack into the child
Require child owner to take ownership of parent stack to keep from deprecation
In the case of multiple child owners, this could include some or all as shared owners of the parent
Acceptance Criteria
[ ] Investigate and select approach for parent stack scenarios
[ ] Create issue to update the deprecation policy to include chosen approach
Which area/kind this issue is related to?
/area releng
Issue Description
Our current deprecation policy under for stack lifecycle is missing the scenarios if a parent stack falls under a deprecation case but has a child stack/sample which is still being maintained. An investigation should be done to see what process would be best to address these scenarios.
Two ideas I have is to:
Acceptance Criteria