Discuss the possibility of occasional semver-minor bumps in LTS about lts HOT 8 CLOSED

@nodejs/lts

from lts.

That sounds reasonable. We should, however, try to establish some kind of rubric for evaluating these things. For instance, changes that improve usability of testing, debugging, support, etc would have preference over changes that simply add new API calls, etc.

from lts.

I agree having the rubric will help, I also wonder if they need to be quarterly or "when appropriate"

from lts.

I agree having the rubric will help, I also wonder if they need to be quarterly or "when appropriate"

We should have some way of stacking them up imo, unlike the stable branch. Just so we don't do like, two in a row for LTS users who may be more on-edge.

from lts.

Dropping them into the staging branches ought to work. We'll just need to
make sure they don't transfer over to the release branches until we're ready
On Dec 4, 2015 10:41 AM, "Jeremiah Senkpiel" [email protected]
wrote:

I agree having the rubric will help, I also wonder if they need to be
quarterly or "when appropriate"

We should have some way of stacking them up imo, unlike the stable branch.
Just so we don't do like, two in a row for LTS users who may be more
on-edge.

—
Reply to this email directly or view it on GitHub
#61 (comment).

from lts.

+1 on getting this better defined. IMO, it is fine to stage/stack these changes, but the schedule needs to be predictable rather than the limbo that the nodejs/node#3609 is in at the moment.

from lts.

Since we have been doing occasional semver minor bumps is it safe to close this?

from lts.

Yes
On Apr 18, 2016 2:34 PM, "Myles Borins" [email protected] wrote:

Since we have been doing occasional semver minor bumps is it safe to close
this?

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub
#61 (comment)

from lts.