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

[TODO] Implement backporting policy configuration #7

Open
webknjaz opened this issue Sep 13, 2020 · 0 comments
Open

[TODO] Implement backporting policy configuration #7

webknjaz opened this issue Sep 13, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@webknjaz
Copy link
Member

webknjaz commented Sep 13, 2020

What I have in mind is having a config structure that would allow the repo to say that the current version is X and the policy for bugfixes is X-1, the policy for security fixes is X-2 (for example).

Then, it'd allow us to implement the flow where having a bug label would trigger backports to the previous version and having security would trigger backports to two previous versions. Alternatively, this could be made explicit with needs_bug_backport / needs_security_backport (via opt-in or opt-out).

The last bit needed is to allow the repo to specify what part of the version spec to consider a bump (whether for v2.1.1 X-1 is considered v1.0.0, or v2.0.0, or v2.1.0).

Depends on: #5
Depends on: #6

Fund with Polar
@webknjaz webknjaz added the enhancement New feature or request label Sep 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant