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.

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

Add backport setups as we now have 1.x branch. #53

Conversation

peterzhuamazon
Copy link
Member

@peterzhuamazon peterzhuamazon commented Apr 25, 2022

Signed-off-by: Peter Zhu [email protected]

Description

Add backport setups as we now have 1.x branch.
Since 2.0.0 is coming I would keep main as 2.x.x and create a new branch 1.x.
The 1.x branch will serve as the active branch for 1.3.x and others in 1.x.

If anyone pushing code that runs on both 1.x and main, they can just open PR to main then add the tag backport 1.x to the PR and the workflow will automatically create backport PR.

If the code is specific to main branch and 2.x.x then they can ignore adding the tag.

Thanks.

Issues Resolved

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Peter Zhu <[email protected]>
@peterzhuamazon
Copy link
Member Author

Close this for now as I think back and probably better let users switch versions directly instead of maintaining a second branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cicd documentation Improvements or additions to documentation release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant