Maintenance: Split maintenance and tech debt tasks

[heitorlessa]

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

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under 2.14.0 version!