Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Move 8.x into maintenance mode in January 2019 #376
how is it possible to have two active LTS releases at the same time? wouldn't that make some confusions for the new coming developers to choose? Also, what does Maintenance mode means? is that something like a Tag that indicates the final days of a release? what's the point of it? thanks in advance.
@AliSawari we need to have overlap so people have time to transition from one LTS release to another.
Maintenance mode means that commits which have landed in master/Current releases are no longer actively backported to the version. Instead only Critical and security fixes are backported.
added a commit
Nov 19, 2018
referenced this issue
Nov 19, 2018
I agree. I also wonder if we're not going to be in the same situation with 10.x and 12.x.
I'm assuming we'll be somehow communicating the change of date ahead of 1 Jan 2019 (so it's not a surprise to anyone not following this repository)? (It's too late, but maybe it should have been with the 8.13.0 release blog).
Was/is there a larger conversation around backporting somewhere? The impression I get is that it's often painful to do. I have a feeling it's also rather thankless work.
From the angle of the package maintenance initiative, it'd be good to collect some knowledge around what works and what doesn't.
related, @MylesBorins I'm not available to help with Node.js releases atm, but I'd like to be a fly on the wall for a future discussion around LTS timelines to better understand what goes into these decisions.