0.3.4 release planning issue - Githubissues

JuliaLang / julia

The Julia Programming Language

https://julialang.org/

MIT License

45.46k stars 5.46k forks source link

0.3.4 release planning issue #9360

Closed staticfloat closed 9 years ago

staticfloat commented 9 years ago

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.

ivarne commented 9 years ago

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 commented 9 years ago

also

[x] https://github.com/JuliaLang/julia/commit/9975b704da6072f71395dd218d47a5fe9e335094 and
[x] https://github.com/JuliaLang/julia/commit/54affdb3f37e8d02c9d6e1806229c4933890a094#diff-8d2b8a22d475d81e3a1944aedb57ad42R413 and
[ ] ~~https://github.com/JuliaLang/julia/commit/8203538c7f621000cf8fc8fa1509c50c2b83a8dd~~ [edit by tkelman - sounds like we decided against this one]

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

tkelman commented 9 years ago

[x] A modified version of d8cf6fe

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 commented 9 years ago

And I'll want to apply

[x] the reverse of https://github.com/JuliaLang/julia/commit/06a7bb99c8f48f31dda2d5b5582f7667ca72515a (included in #9376)

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 commented 9 years ago

[x] ee4d1f284e290ec6f11c44b2964032069dac66d3 (thanks @jey)
[x] 1d8e162
[x] 9c7a490b348
[x] 0c48dd8332fcb2100e8b02710339c27bbe425943
[x] 04271cd51909d8220f08c6fc56031a47959032b5
[x] 0b44aca52b968b0937739021dd65593589a462fd and ed5a8fcb93dbf12da53a51448251ec8c9dfedc42 and a2ff1ea5a17fd1df930d662247b15428a9198c3d and 0050b725d6052a72e8d1a07cce84238374fff153
[x] 2841decc3bebd784b73685930b16f6a9845ee3f7 and a3d95db08e1ad11b38147a2054f8fec59937b142

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

tkelman commented 9 years ago

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

tkelman commented 9 years ago

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 commented 9 years ago

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

ivarne commented 9 years ago

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

tkelman commented 9 years ago

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

staticfloat commented 9 years ago

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 https://github.com/JuliaLang/julia/issues/9360#issuecomment-68121148.

tkelman commented 9 years ago

closed by 33920266908e950936ef3f8503810a2d47333741, thanks E! :santa: