-
Notifications
You must be signed in to change notification settings - Fork 550
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
[node] Deprecate GLOBAL in favor of global #1880
Conversation
The `GLOBAL` variable should not be used in order to avoid `DeprecationWarning: 'GLOBAL' is deprecated, use 'global'`.
What's up with C code failing to build on this? 😕 |
I think that CI failure is unrelated to your change. We've had various failures in the past because of Travis changing their environment. This looks like one of them. Do you know from which Node.js version |
This commit was released in v6.0.0 according to the tags and this discussion due to the |
As a side question, what is the SupportCentral label all about? |
SupportCentral is a tool that we wrote and use internally for keeping track of which Github issues require a reply from us. It uses that label for keeping track. You can ignore the label. |
What's the usual timeline for PRs for Passenger? When should I expect some response here? |
@sigv There is no usual timeline, we try to look at them all but it depends on the urgency of a certain PR. One thing to note is that you shouldn't PR against master, but instead against stable. |
@OnixGH Fair enough. I thought |
The contributor's guide indeed says that changes should go to stable branches, so that's a mistake on my part; sorry! The question still stands. |
@sigv not sure what answer you are looking for, but we don't have a timeline. Edit: Oh, maybe you meant about stable? Yes please! |
@OnixGH Oh, sorry for the misunderstanding. Yeah I meant - the question still stands about branches. Will resubmit in that case. |
The
GLOBAL
variable should not be used in order to avoidDeprecationWarning: 'GLOBAL' is deprecated, use 'global'
.