-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
0.3.3 release planning issue #9045
Comments
Should we backport #8734 ? @ViralBShah bumped OpenBLAS to v0.2.12 on release-0.3 for performance reasons, but I don't think we've backported the ILP64 compatibility fix (and subsequent makefile fixups). release-0.3 has been pretty quiet for a few weeks. Here's a quick scan of some things from master that might be backport-worthy? Sorry for the massive ping, add the Also when it comes time to build the release binaries, it might be good to use a dedicated script to do so, instead of recycling the nightly build scripts which have been diverging a bit. |
There have been a few documentation improvements recently. Should those be backported as well? |
@tknopp that one was backported by @ivarne in 5dda348 @ViralBShah any doc improvements that apply to release-0.3, yeah. Want to skim through the commit list and find any that haven't been backported yet? |
d9fb7e0 - the correction to |
@amitmurthy thanks, done in 28e5f11 |
I think that all doc related issues now are either backported or have the pending label. |
Okay, last thing on my list is #9050 then I think it's ready, modulo a few days of people other than me testing the big pile of backports I've pushed. |
we haven't tagged yet, but are those performance improvements or bugfixes? we haven't been backporting many other things that are just for performance afaik |
It would be nice to get in #8889 as well, I'm trying to find out why the Linux Travis build fails. |
We have backported performance fixes in the past, and I think those are prime candidates because they don't have the potential to break user code. Then we have the issue of just sneaking in new functionality right before a release (especially functionality that fails on Linux). We would have to delay the release so that we have more time for |
#8889 is pretty innocuous. It passes on all platforms now that it's equipped to handle Git's plethora of decimals. I'm going to backport that, then start the @vtjnash I think your two commits above are the only things in this discussion that are still undecided on. I don't know how your commits will effect stability, and I can't backport them as they have merge conflicts on It'd also be nice if someone could take a pass at the commit log since |
innocuous = contains 0.4-only syntax... @staticfloat when you say "all platforms," did you test on all platforms? Calling
Please don't tag 0.3.3 until we're sure it works. |
Better, but I still get the ENOENT on Windows. |
i think we want JuliaLang/libuv#27 also. i forgot that it wasn't already merged, since I saw that it had merged upstream |
That even made it into libuv 1.0.0 which was just tagged a couple days ago. But considering it's not even merged in our fork and has been tested by probably at most 1 or 2 people with Julia, I would say it's 0.3.4 material at best. Unless we want to hold off another week or so for 0.3.3. |
I got the pkg test at least not showing any new failure modes that didn't exist in 0.3.2 on Windows, but I realize it still fails on 0.3 since we never backported #7590 - that was one of the first few 0.4 commits, it's a bit feature-y but also resolves a bug of not being able to delete read-only files (#7573). I'm a little on the fence about backporting it now vs first thing for 0.3.4, it's seemed stable enough for the past 3 months on master. |
Thank you everyone for taking care of the syntax error I introduced on |
I have an insane |
@staticfloat Updated |
no we didn't backport the virtualenv stuff. we could consider it for 0.3.4 maybe? |
Alright, |
Fedora/EPEL RPMs are now in the Copr repo. |
this removes the last hash table used by de-serialization in favor of a direct array
Thanks for your efforts everybody! Another release down. :) |
Yes, kudos to everyone helping the 0.3 releases. I think they definitely help keep a feel of "continuous" updating that was lacking in the 0.2 cycle (i.e. one big release and then nothing for a long time until 0.3 was released). |
That doctored up mem is brilliant. |
Love it! |
Our monthly stable release is looming. Please discuss the inclusion of issues into this release that haven't already been merged. The 0.3.3 milestone is set for Nov 21st, so let's shoot for that barring any big discussions on what to include.
The text was updated successfully, but these errors were encountered: