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

0.3.4 release planning issue #9360

Closed
staticfloat opened this issue Dec 14, 2014 · 12 comments
Closed

0.3.4 release planning issue #9360

staticfloat opened this issue Dec 14, 2014 · 12 comments
Milestone

Comments

@staticfloat
Copy link
Member

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.

@staticfloat staticfloat added this to the 0.3.4 milestone Dec 14, 2014
@ivarne
Copy link
Member

ivarne commented Dec 14, 2014

We have a healthy 10 issues labeled backport pending. Some of them should probably be on the milestone instead, because they need more work than just some time to test on master and a cherry-pick.

@vtjnash
Copy link
Member

vtjnash commented Dec 14, 2014

also

which are each tagged individually, but still likely need to be backported

@tkelman
Copy link
Contributor

tkelman commented Dec 15, 2014

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)

@tkelman
Copy link
Contributor

tkelman commented Dec 15, 2014

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.

@tkelman
Copy link
Contributor

tkelman commented Dec 15, 2014

(the backport pending label is just so this issue conveniently shows up in the same search)

tkelman referenced this issue Dec 19, 2014
pass a stack-copy of ctxThread in jl_throw_in_ctx to rec_backtrace_ctx
@tkelman
Copy link
Contributor

tkelman commented Dec 24, 2014

I think the status here is we're waiting for me to finish getting #9376 working on Windows, in case anyone was wondering.

@tkelman
Copy link
Contributor

tkelman commented Dec 25, 2014

As far as backport pending issues go, my vote would be for holding off on #8388 and #9063 until shortly after tagging. There's a PCRE version question on #8388, and #9063 hasn't been on master for very long, so I'd prefer more testing time on release-0.3 in both cases.

@tkelman
Copy link
Contributor

tkelman commented Dec 25, 2014

I have a crap version of sphinx, can someone else regenerate helpdb.jl? We should maybe backport 10b64dd early next cycle.

@ivarne
Copy link
Member

ivarne commented Dec 25, 2014

Updated helpdb.jl in cec019442 (sorry, posted too soon, it's in 2496766)

@tkelman
Copy link
Contributor

tkelman commented Dec 26, 2014

doc/manual/strings.rst doesn't go into helpdb.jl at all, does it? If not, are we good to tag?

@staticfloat
Copy link
Member Author

I think so. I'm running release-candidate now just to double-check. When
it passes, I will tag.
-E

On Thu, Dec 25, 2014 at 7:38 PM, Tony Kelman notifications@github.com
wrote:

doc/manual/strings.rst doesn't go into helpdb.jl at all, does it? If not,
are we good to tag?


Reply to this email directly or view it on GitHub
#9360 (comment).

@tkelman
Copy link
Contributor

tkelman commented Dec 26, 2014

closed by 3392026, thanks E! 🎅

@tkelman tkelman closed this as completed Dec 26, 2014
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

No branches or pull requests

4 participants