-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Where's Christopher? #92
Comments
No apologize necessary, Christopher. Personal matters always comes first by my book! Thanks for letting us know and best wishes to you. I have been watching nodejs/node#4857 closely. I may have limited Internet access in case of an emergency release during the weekend, but I will be back with full Internet access Sunday night UTC time to make sure we get the patches out as quickly as possible (unless someone beats me to it). Should we ping the Docker Library guys to let them know of the pending patch release? |
Thank you :) For Docker, yes, I think pinging them would be good to give them advance notice. Also for the pull request to the library, the consensus on docker-library/official-images#1240 was that we should add a |
❤️ ❤️
|
Closing this out because I'm more or less "back" :) |
Welcome back ❤️ |
Hi @nodejs/docker ,
I'm going to be unavailable for a week or so to deal with some personal matters. I wanted to let everyone know in light of https://nodejs.org/en/blog/vulnerability/openssl-and-low-severity-fixes-jan-2016/ as I most likely won't be able to handle the updates for 0.10.x and 0.12.x :(
Also, apologies for the extraneous issue here. I wasn't sure what the best way was to keep everyone informed...
The text was updated successfully, but these errors were encountered: