-
Notifications
You must be signed in to change notification settings - Fork 578
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
doc: add minutes for meeting 2017-05-15 #217
Conversation
doc/meetings/2017-05-15.md
Outdated
- All: agreed | ||
- Myles: I think the bigger issue is that we are inconsistent about how stable | ||
current is, and whether it’s recommended for more general use. | ||
- Myles to raise CTC issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we actually agreed to what was captured in this comment: #128 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you talking about this line (Myles to raise CTC issue
) or
Myles: We could say: “After the next Current release line comes out, there will be no more scheduled releases. Further releases will be agreed on a case-by-case basis.”
?
The CTC issue is a more general question about whether we recommend people use Current releases.
If you want to change what it says that Myles said on L45, then feel free to just edit this PR!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ping @mhdawson
Update to clarify agreement on "what happens with odd-numbered releases in April"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edited and LGTM.
PR-URL: nodejs#217 Fixes: nodejs#213
Fixes: #213