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

[Ops] Add official ability to target specific versions in backport #163294

Closed
watson opened this issue Aug 7, 2023 · 2 comments
Closed

[Ops] Add official ability to target specific versions in backport #163294

watson opened this issue Aug 7, 2023 · 2 comments
Labels
Team:Operations Team label for Operations Team

Comments

@watson
Copy link
Contributor

watson commented Aug 7, 2023

Sometimes it's desirable to backport a PR to the previous major without having to also backport it to the previous minor. Today this is technically possible using the label auto-backport combined with specific v* labels. However, this label is technically deprecated and it's recommended to use the backport:* labels instead. But none of these support this use-case (contrary to what I originally believed, backport:prev-MAJOR will backport to the previous major AND any open branch in between).

So I propose a new label along the lines of backport:selected-versions or backport:specific-versions or something shorter - I don't like it's so long.

Background

I imagine this is mainly needed when backporting tooling PRs. Here you don't really care about the previous minor because it's so short lived, whereas it's important to keep the previous major in sync with main since it's going to be around for so long.

Example for a situation recently where I needed this, and where I first tried to use backport:all-open, but had to undo it because the backport to 8.9 was causing too many problems: #162464

@watson watson added the Team:Operations Team label for Operations Team label Aug 7, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@jbudz
Copy link
Member

jbudz commented Oct 1, 2024

@jbudz jbudz closed this as completed Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

3 participants