The release schedule: https://github.com/nodejs/Release
The documentation states: lts/*
latest LTS Node.js release
It could be a different strategy is actually used, in that case the documentation should become something like: lts/*
oldest active LTS Node.js release
According to https://github.com/nodejs/Release/blob/38e0ec2c9e4bf889cccb46a343bf3baccc683ba1/schedule.json#L46-L52 (current as of 2018-10-26), 10.x has not yet reached the LTS status.
"v10": {
"start": "2018-04-24",
"lts": "2018-10-30",
"maintenance": "2020-04-01",
"end": "2021-04-01",
"codename": ""
}
So this behavior seems correct to me.
Yeah, you are right! I must have looked at that scheme a few days ago: https://github.com/nodejs/Release/commit/bc532989696ceb3e612c0f998106616c9020ba64
1 Like