Skip to content

[cherry-picker] Misleading assumption about backport branches naming #251

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
Closed
webknjaz opened this issue May 23, 2018 · 0 comments
Closed

[cherry-picker] Misleading assumption about backport branches naming #251

webknjaz opened this issue May 23, 2018 · 0 comments
Labels
cherry_picker.py

Comments

@webknjaz
Copy link
Contributor

While it's true for cpython and aiohttp, not everyone uses just version numbers for their backport branches.

Someone may use v-prefix v2.6, we use stable-2.6. There might be other cases.
I suggest changing how version is extracted from the branch name, so that it would support more generic flows.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cherry_picker.py
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@webknjaz @Mariatta