-
Notifications
You must be signed in to change notification settings - Fork 570
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: fix meeting minute dates #255
Conversation
In the case of 2017-04-24.md, 2017-03-13.md suggests that April 4 might have been correct and it was the filename that was wrong. The rest looks good, assuming that these are the correct dates :) |
Ah, from #201 it seems like 24 was indeed correct. |
f5f49d7
to
9967148
Compare
Good point, adjusted the |
doc/meetings/2017-06-26.md
Outdated
@@ -3,7 +3,7 @@ | |||
- [Github Issue](https://github.com/nodejs/LTS/issues/233) | |||
- [Meeting Video](https://www.youtube.com/watch?v=xSo6YiKzc5M) | |||
- [Previous meeting](https://github.com/nodejs/LTS/issues/225) | |||
- Next meeting: 17 July 2017 | |||
- Next meeting: 19 July 2017 |
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.
Should be 19 September?
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.
Not sure what I was doing here, it should actually have been the 17th of July, see #235.
The meeting was cancelled, but we didn't know that at the time.
9967148
to
67b485a
Compare
Looks good now 👍 |
Fixes: #253
cc/ @mjomble, let me know if this LGTY.
You can check the meeting issues here: https://github.com/nodejs/Release/issues?q=is%3Aissue+is%3Aclosed+label%3Alts-meeting