Currently we have been not particularly exact about when we do Semver-Minor releases on LTS branches. The only real guideline has been "not too often". My impression was that we wanted to space out Semver-Minor releases to avoid LTS feeling like it was moving too fast (which seems fairly reasonable to me).
We have found ourselves in a position where a change has landed into Core, and soon in a Current Release, that solves an edge cases for users behind firewalls and needing to use proxies
nodejs/node#9139
We could likely do a Semver-Minor release of Boron but having just cut a minor of Argon I was hesitant to follow up with yet another minor.
There are also practical reasons for holding off on another minor release, particularly waiting for a bit more of a backlog.
I'd like to hear people's opinions regarding Semver-Minor changes.
Currently we have been not particularly exact about when we do
Semver-Minorreleases on LTS branches. The only real guideline has been "not too often". My impression was that we wanted to space outSemver-Minorreleases to avoid LTS feeling like it was moving too fast (which seems fairly reasonable to me).We have found ourselves in a position where a change has landed into Core, and soon in a Current Release, that solves an edge cases for users behind firewalls and needing to use proxies
nodejs/node#9139
We could likely do a
Semver-Minorrelease ofBoronbut having just cut a minor ofArgonI was hesitant to follow up with yet another minor.There are also practical reasons for holding off on another minor release, particularly waiting for a bit more of a backlog.
I'd like to hear people's opinions regarding
Semver-Minorchanges.