Maintenance: Document how to maintain the release process of v1 and v2

[rubenfonseca]

Summary

We need to make sure that the v1 and v2 release processes can still work after the release of v2.

Why is this needed?

We want to keep maintaining v1 for bug fixing only for some time, and be able to release new versions of it when necessary.

Which area does this relate to?

Governance

Solution

Fork develop into v1 before we merge the v2 branch.
Use develop as the main development branch.
Update all workflows so we can still release v1 when necessary, without interfering with v2.

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.