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

[node] Deprecate GLOBAL in favor of global #1880

Closed
wants to merge 1 commit into from
Closed

[node] Deprecate GLOBAL in favor of global #1880

wants to merge 1 commit into from

Conversation

sigv
Copy link
Contributor

@sigv sigv commented Oct 6, 2016

The GLOBAL variable should not be used in order to avoid DeprecationWarning: 'GLOBAL' is deprecated, use 'global'.

The `GLOBAL` variable should not be used in order to avoid
`DeprecationWarning: 'GLOBAL' is deprecated, use 'global'`.
@sigv
Copy link
Contributor Author

sigv commented Oct 6, 2016

What's up with C code failing to build on this? 😕

@sigv
Copy link
Contributor Author

sigv commented Oct 6, 2016

This looks very much like the failure for 3306cad (that's the current master^). Is there some underlying bug with the project or the CI in particular?
I really do not see how C compiler can fail due to this change.

@FooBarWidget
Copy link
Member

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 GLOBAL was deprecated in favor of global?

@sigv
Copy link
Contributor Author

sigv commented Oct 6, 2016

This commit was released in v6.0.0 according to the tags and this discussion due to the GLOBAL never having been actually documented.

@sigv
Copy link
Contributor Author

sigv commented Oct 6, 2016

As a side question, what is the SupportCentral label all about?

@FooBarWidget
Copy link
Member

FooBarWidget commented Oct 6, 2016

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.

@sigv
Copy link
Contributor Author

sigv commented Oct 7, 2016

What's the usual timeline for PRs for Passenger? When should I expect some response here?

@OnixGH
Copy link
Contributor

OnixGH commented Oct 7, 2016

@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.

@sigv
Copy link
Contributor Author

sigv commented Oct 7, 2016

@OnixGH Fair enough. I thought master was the development branch and, well, new changes should go into the development branch right away. Should I make a new PR for a stable branch?

@sigv
Copy link
Contributor Author

sigv commented Oct 7, 2016

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.

@OnixGH
Copy link
Contributor

OnixGH commented Oct 7, 2016

@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!

@sigv
Copy link
Contributor Author

sigv commented Oct 7, 2016

@OnixGH Oh, sorry for the misunderstanding. Yeah I meant - the question still stands about branches. Will resubmit in that case.

@sigv sigv closed this Oct 7, 2016
@sigv sigv deleted the node-deprecate-global branch October 7, 2016 17:03
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.

3 participants