-
Notifications
You must be signed in to change notification settings - Fork 506
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
Release 2.1.0 #446
Comments
+1 that's a good list for 2.1 |
@kkoopa That pull request have been merged now, time to cut a release? 👍 |
Yes, I'll get on to it this week. On September 21, 2015 2:47:00 PM GMT+03:00, "Linus Unnebäck" notifications@github.com wrote:
|
Thank you! |
+1 Thank you! Very much looking forward to it! |
So what else is needed for nan v2.1? If you have any outstanding issues I can take a shot at them and send you some PRs. |
I had two computers die within one week of eachother, which prevented me from doing it this week. Now I am in Barcelona for a week and can't make a release until I'm back. Sorry, but shit happens. If there's a rush, @rvagg can make a release to npm, else I'll deal with it in a week. On September 26, 2015 3:42:26 AM GMT+02:00, Mikola Lysenko notifications@github.com wrote:
|
That's too bad :( No stress, hope you get your computer situation sorted. Having your computer die on you is never fun. |
Figured I'd get this out some time after Node 4.0.0 was released. Currently waiting on nodejs/node#2698 for no other reason than 'because'. Expect a release this week. It will contain the four PRs scheduled for 2.1. Nothing really significant.
The text was updated successfully, but these errors were encountered: