Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
1 of 2 tasks
rubenfonseca opened this issue Oct 19, 2022 · 2 comments · Fixed by #1621, #1624 or #1633
Closed
1 of 2 tasks

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

rubenfonseca opened this issue Oct 19, 2022 · 2 comments · Fixed by #1621, #1624 or #1633
Assignees
@rubenfonseca
Labels
internal Maintenance changes

Comments

@rubenfonseca
Copy link
Contributor

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
@rubenfonseca rubenfonseca added triage Pending triage from maintainers internal Maintenance changes and removed triage Pending triage from maintainers labels Oct 19, 2022
@rubenfonseca rubenfonseca self-assigned this Oct 19, 2022
This was referenced Oct 19, 2022
Merged
Merged
@rubenfonseca rubenfonseca linked a pull request Oct 19, 2022 that will close this issue
chore(ci): prepare CI actions for v1 releases #1621
Merged
7 tasks
@github-actions github-actions bot added the pending-release Fix or implementation already in dev waiting to be released label Oct 20, 2022
@rubenfonseca rubenfonseca mentioned this issue Oct 20, 2022
Merged
7 tasks
@rubenfonseca rubenfonseca linked a pull request Oct 20, 2022 that will close this issue
feat(ci): release docs as alpha when doing a pre-release #1624
Merged
7 tasks
@github-actions
Copy link
Contributor

⚠️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.

@heitorlessa heitorlessa removed the pending-release Fix or implementation already in dev waiting to be released label Oct 20, 2022
@rubenfonseca rubenfonseca mentioned this issue Oct 21, 2022
Merged
7 tasks
@rubenfonseca rubenfonseca linked a pull request Oct 21, 2022 that will close this issue
fix(ci): remove v2 suffix from SAR apps #1633
Merged
7 tasks
@github-actions github-actions bot added the pending-release Fix or implementation already in dev waiting to be released label Oct 21, 2022
@github-actions
Copy link
Contributor

This is now released under 2.0.0a3 version!

@github-actions github-actions bot removed the pending-release Fix or implementation already in dev waiting to be released label Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rubenfonseca rubenfonseca

Labels
internal Maintenance changes
Projects
None yet
Milestone
No milestone
2 participants
@rubenfonseca @heitorlessa