Maintenance: Update roadmap April

[heitorlessa]

Summary

Update roadmap for April

Why is this needed?

Roadmap is out of date

Which area does this relate to?

Governance

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[heitorlessa]

@dreamorosi @am29d - I've tried creating an automated report and noticed feature-request label used in other languages is named type/feature-request in TS -- can I get your help to rename it, please?

There might be others in the future like internal, but not being used in the reporting yet.

[dreamorosi]

Yes, all the labels we use are scoped, I set them up like this over a year ago to be a bit more informative, like:

• what's the type of issue: feature-request, bug, internal, etc.
• what's the area: logger, tracer, etc
• what's the status: pending-release, complete, etc.

I did this when we created the public project and I manually went through all the existing GH issues & PRs, including closed ones, to apply the new conventions.

Is there any chance that we can extend the report automation to take in account a map/dictionary that lets the repo set their own labels? The action would be centralized, but when running it can load a file at .github/labels.yml that contains a mapping.

What do you think?

If it's too much work, or we have a need to align the labels among projects (understandable), I'll set aside a couple of hours today and change all the labels back.

As you mentioned offline, changing the labels in the "Labels" tab applies to all existing labels, so it's much less effort. I have updated the labels and I'll open a new PR to update the maintainers handbook and other automation that relies on labels.

[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 v2.1.1 version!