Skip to content

[node] Deprecate GLOBAL in favor of global - #1880

Closed
sigv wants to merge 1 commit into
phusion:masterfrom
sigv:node-deprecate-global
Closed

[node] Deprecate GLOBAL in favor of global#1880
sigv wants to merge 1 commit into
phusion:masterfrom
sigv:node-deprecate-global

Conversation

@sigv

@sigv sigv commented Oct 6, 2016

Copy link
Copy Markdown
Contributor

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

sigv commented Oct 6, 2016

Copy link
Copy Markdown
Contributor Author

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

@sigv

sigv commented Oct 6, 2016

Copy link
Copy Markdown
Contributor Author

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
Copy Markdown
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

sigv commented Oct 6, 2016

Copy link
Copy Markdown
Contributor Author

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

sigv commented Oct 6, 2016

Copy link
Copy Markdown
Contributor Author

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

@FooBarWidget

FooBarWidget commented Oct 6, 2016

Copy link
Copy Markdown
Member

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

sigv commented Oct 7, 2016

Copy link
Copy Markdown
Contributor Author

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

@OnixGH

OnixGH commented Oct 7, 2016

Copy link
Copy Markdown
Contributor

@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

sigv commented Oct 7, 2016

Copy link
Copy Markdown
Contributor Author

@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

sigv commented Oct 7, 2016

Copy link
Copy Markdown
Contributor Author

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

OnixGH commented Oct 7, 2016

Copy link
Copy Markdown
Contributor

@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

sigv commented Oct 7, 2016

Copy link
Copy Markdown
Contributor Author

@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