-
Notifications
You must be signed in to change notification settings - Fork 570
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
Current status of LTS group/ backporters #1012
Comments
There's some previous discussion in #912. That also proposed removing backporters. As I mentioned in #912 (comment) the I think it's fair to have a discussion as to whether the Lines 93 to 95 in 17c98b4
and I guess it's debatable whether you can manage the process/content for releases without being a releaser or backporter. You could certainly have an opinion on what could/should be in a LTS release line and how often releases should happen as a general consumer of Node.js. One thing I would stress is that membership of the Release WG does not equate to being a releaser: Lines 81 to 87 in 17c98b4
|
In meeting #1026 we had consensus about removing the @nodejs/lts team, and merge it into @nodejs/releasers |
Quoting documentation https://github.com/nodejs/Release/blob/main/GOVERNANCE.md:
LTS:
Backporters https://github.com/nodejs/Release?tab=readme-ov-file#lts-staging-branches:
Currently we are not enforcing both of these rules.
I think we should remove the LTS team and keep only releasers, and keep the backporters for people who want to start getting involved with the release working group and can prepare current releases.
The text was updated successfully, but these errors were encountered: