Skip to content

Prefer the parent module when serializing functions (fixes #13452) #13455

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

Merged
merged 1 commit into from
Oct 6, 2015

Conversation

timholy
Copy link
Member

@timholy timholy commented Oct 5, 2015

I've verified that this works on 0.4.0-rc4, so @JuliaBackports.

@tkelman
Copy link
Contributor

tkelman commented Oct 5, 2015

where does this rank in criticality? must do for final, or could wait for next point release?

@timholy
Copy link
Member Author

timholy commented Oct 5, 2015

I'm fine if we wait for point release---people like me can fix locally, there hasn't been a barnstorming of complaints about this, and I'm as excited as anyone to get 0.4 out.

FYI, those lines were last touched in 74b0488 and 015401d. CC @JeffBezanson.

JeffBezanson added a commit that referenced this pull request Oct 6, 2015
Prefer the parent module when serializing functions (fixes #13452)
@JeffBezanson JeffBezanson merged commit 128f8c6 into master Oct 6, 2015
@timholy timholy deleted the teh/serialize_func_modscope branch October 6, 2015 18:58
@tkelman tkelman added this to the 0.4.1 milestone Oct 7, 2015
@timholy
Copy link
Member Author

timholy commented Oct 16, 2015

If I wanted to get this into the release-0.4 queue, what's the proper procedure? Submit a cherry-pick PR against release-0.4, or are you staging these on some other branch?

@tkelman
Copy link
Contributor

tkelman commented Oct 16, 2015

The label is the right procedure. I haven't started staging things for 0.4.1 yet, I consider #13550 release blocking. I will do a staging branch where I run PkgEval on code changes before merging them to release-0.4.

@timholy
Copy link
Member Author

timholy commented Oct 17, 2015

Your care in managing these releases is greatly appreciated.

@tkelman
Copy link
Contributor

tkelman commented Oct 17, 2015

It's been working out pretty well so far 😀

Though I'm a little ashamed I let #13550 slip through without noticing beforehand, but the download numbers for 32 bit linux are the lowest of any of the platforms we regularly build binaries for so at least it isn't hitting too many users.

@timholy
Copy link
Member Author

timholy commented Oct 17, 2015

It's been working out pretty well so far 😀

I'd rate that as an understatement; perhaps it's just that the most vocal people were already running 0.4, but the relative lack of "this broke my code!" reports is quite amazing.

timholy added a commit that referenced this pull request Oct 31, 2015
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