meta: label for pre-backport request

[joyeecheung]

Spun off from #16249 , I think we can add a label and use it first to see how it goes. I am not really a master at naming things, maybe should-prebackport?

[apapirovski]

Could be something like prebackport-requested-vXYZ... I'm guessing there'll be some that need multiple prebackports and others that don't. But I'm bad at naming so y'kno... 😅

[lance]

On a related note (and maybe I should just create an issue for this), I have been doing a few backports in the past week, and I'm not 100% clear on how issues should be labeled when submitting a backport PR. The docs say "After the PR lands replace the backport-requested-v6.x label on the original PR with backported-to-v6.x.". This makes sense to me.

However, I noticed in #16020 (comment) that it was labeled backported-to-v8.x in spite of the backport PR still being open. Maybe it was just a mistaken slip of a click. But I think it would be useful to have a label marking the original PR as having been backported to a staging pull request, but that staging PR has not yet landed. For those doing the work to get commits from vX.x-staging to vX.x it seems like it would be useful to find what work needs to be done. And for those doing the work to backport the PRs to staging, it's helpful for filtering out those that have already been backported.

[joyeecheung]

cc @nodejs/lts

[gibfahn]

Spun off from #16249 , I think we can add a label and use it first to see how it goes. I am not really a master at naming things, maybe should-prebackport?

Couldn't we just use the existing backport-requested labels? I don't think there's any difference between a pre-backport and a backport other than the fact that it's requested before the PR lands.

However, I noticed in #16020 (comment) that it was labeled backported-to-v8.x in spite of the backport PR still being open. Maybe it was just a mistaken slip of a click. But I think it would be useful to have a label marking the original PR as having been backported to a staging pull request, but that staging PR has not yet landed.

I see the use, but it's yet more manual effort for the backporter, and also more complexity for people to learn to understand the process. I think I'd be okay with it if it could be automated. Also we really want to be landing backport PRs within 24 hours, otherwise they tend to get stale.

[joyeecheung]

Couldn't we just use the existing backport-requested labels? I don't think there's any difference between a pre-backport and a backport other than the fact that it's requested before the PR lands.

Oh right, haven't thought about that....

I see the use, but it's yet more manual effort for the backporter, and also more complexity for people to learn to understand the process. I think I'd be okay with it if it could be automated.

Added to my backlog..

[joyeecheung]

I am going to close this because I think we can just use backport-requested labels for now.