Closed
Description
Summary
Today we use maintenance (internal label) tasks as an umbrella for an array of activities related to governance, automation, and general tech debt.
Idea here is to create a separate template and label to more easily assess whether we are making progress in making the ever growing code base easier to maintain, therefore increasing our delivery velocity and security.
Why is this needed?
We cannot quantify whether we're making progress in addressing technical debt. This will help us improve how we balance our efforts, so we don't get accidentally blocked when adding new features because of complexities introduced for various reasons.
Which area does this relate to?
Other
Solution
Create a new issue template, a new label, and update maintenance template to remove tech debt wording AND Maintainers playbook.
Acknowledgment
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript