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

Remove unused attempt backport script #288

Merged
merged 1 commit into from
May 2, 2021

Conversation

phillipj
Copy link
Member

This was a very neat part of the bot at one point (#77), but ended up creating some noise and parts got disabled (#118).

It used to try backport of patches from created & updated PRs against the ${version}.x-staging branches and as a result, added lts-watch-v${version}.x or dont-land-on-v${version}.x when applicable.

When it was operational, it tried to apply PR patches against Node.js versions: 4, 6 and 7. Those version are all end-of-life now.

For the bot to try backport of patches for newer versions of Node.js, those versions would have to be added explicitly in the bot' source code. That has obviously not happened, assuming the reason being it wasn't as helpful afterall.

@phillipj phillipj requested a review from a team as a code owner November 15, 2020 00:22
This was a very neat part of the bot at one point, but ended up creating
some noise and got disabled.

It used to try backport of patches from created & updated PRs against
the `${version}.x-staging`s and as a result, added
`lts-watch-v${version}.x` or `dont-land-on-v${version}.x` when
applicable.

When it was operationale, it tried to apply patches against Node.js
versions: 4, 6 and 7. Those version are all end-of-life now.

For the bot to try backport of patches for newer versions of Node.js,
those versions would have to be added explicitly in the bot' source code.
That has obviously not happened, assuming the reason being it wasn't
as helpful afterall.
@richardlau
Copy link
Member

I'd completely forgotten we'd tried this before. Not sure if the other current members of @nodejs/releasers are aware of this either/think this would be useful to resurrect in an updated form (maybe instead of lts-watch-* labels it could focus on backport-requested-*?).

I have a vague recollection that @codebytere may have mentioned that Electron has a bot that does something similar?

@phillipj
Copy link
Member Author

@nodejs/releasers you think it would be useful this resurrect this, ref @richardlau's comment above?

If not, I'd really appreciate if we could sunset this code for now. We can always dig it back up again later if needed..

@phillipj
Copy link
Member Author

phillipj commented May 2, 2021

Since no objections were made, I'm merging this to remove this unused part of the source code for now.

@phillipj phillipj merged commit ed45dd5 into nodejs:master May 2, 2021
@phillipj phillipj deleted the remove-attempt-backport branch May 2, 2021 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants