-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Update backporting-to-release-lines.md? #19491
Comments
cc @MylesBorins @nodejs/backporting |
I think adding a couple of lines in the What should be backported makes sense. What should be backported is basically "anything that a release team member wanted to backport but had merge conflicts when it was cherry-picked to a release line". |
Going to close this out given the lack of movement. Feel free to reopen if you believe this is important but in that case... maybe consider a PR instead? |
Should there be info about why particular pull request should be backported or not? And in which branches?
Or maybe not in backporting-to-release-lines.md but somewhere else?
Ref #18357 (comment)
The text was updated successfully, but these errors were encountered: