sesheta
commented
1 year ago Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Have a stability policy which defines how service creators and maintainers handle full or partial system upgrades in a way that changes are transparent to the user - either backwards compatible or automatically migrated. Have a documented procedure how to handle when this is not possible - manual migration guides, deprecation timeframe etc.