-
-
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.4 release planning issue #9360
Comments
We have a healthy 10 issues labeled |
also
which are each tagged individually, but still likely need to be backported |
will be needed to keep appveyor happy in the process of backporting the various recent suitesparse fixes (which are all labeled PR's I believe) |
And I'll want to apply
unless win32 backtraces with sys.dll are going to include file and line number information. We'll have to test to make sure a backported version of #8074 works so users who want fast startup but don't mind degraded backtraces can choose to generate sys.dll themselves. |
I think the status here is we're waiting for me to finish getting #9376 working on Windows, in case anyone was wondering. |
I have a crap version of sphinx, can someone else regenerate helpdb.jl? We should maybe backport 10b64dd early next cycle. |
Updated helpdb.jl in |
|
I think so. I'm running release-candidate now just to double-check. When On Thu, Dec 25, 2014 at 7:38 PM, Tony Kelman notifications@github.com
|
closed by 3392026, thanks E! 🎅 |
Our monthly stable release is looming. Please discuss the inclusion of issues into this release that haven't already been merged. The 0.3.4 milestone is set for Dec 23rd, so let's shoot for that barring any big discussions on what to include.
As of the time of this writing, there are only two other issues beside this one that are specifically slated for 0.3.4.
The text was updated successfully, but these errors were encountered: