Skip to content
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

Discuss the possibility of occasional semver-minor bumps in LTS #61

Closed
Fishrock123 opened this issue Dec 4, 2015 · 8 comments
Closed

Comments

@Fishrock123
Copy link
Contributor

Bringing this up due to nodejs/node#3609 and nodejs/node#4135, of which we've assessed the impact to be minimal in risk, but great in potential benefit.

Perhaps we could have occasional minor bumps on LTS lines to include these sorts of features we've carefully selected.

I suggest we do assessments quarterly to see if we should do a minor bump.

@Fishrock123
Copy link
Contributor Author

@nodejs/lts

@jasnell
Copy link
Member

jasnell commented Dec 4, 2015

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.

@mhdawson
Copy link
Member

mhdawson commented Dec 4, 2015

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

@Fishrock123
Copy link
Contributor Author

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.

@jasnell
Copy link
Member

jasnell commented Dec 4, 2015

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" notifications@github.com
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).

@ofrobots
Copy link

ofrobots commented Dec 4, 2015

+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.

@MylesBorins
Copy link
Contributor

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

@jasnell
Copy link
Member

jasnell commented Apr 18, 2016

Yes
On Apr 18, 2016 2:34 PM, "Myles Borins" notifications@github.com 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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants