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

doc: clarify maintenance period for odd releases #220

Merged
merged 1 commit into from
May 28, 2017

Conversation

gibfahn
Copy link
Member

@gibfahn gibfahn commented May 18, 2017

i.e. that there isn't one.

This was agreed in the LTS meeting: #213

Continuation of #128

i.e. that there isn't one.

This was agreed in the LTS meeting: nodejs#213
@gibfahn
Copy link
Member Author

gibfahn commented May 18, 2017

@nodejs/lts please weigh in.

cc/ @rvagg

Copy link
Member

@jasnell jasnell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm. Not 100% happy with it but it's good enough and can't think of how to make it better. :)

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gibfahn gibfahn merged commit 1ce9499 into nodejs:master May 28, 2017
@gibfahn gibfahn deleted the odd-maintenance branch May 28, 2017 12:16
ChALkeR pushed a commit to ChALkeR/LTS that referenced this pull request Jun 30, 2018
i.e. that there isn't one.

This was agreed in the LTS meeting: nodejs#213

PR-URL: nodejs#220
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
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

Successfully merging this pull request may close these issues.

4 participants