Julia v1.5.0-rc2 is now available

Greetings! May I interest you in a fresh, new Julia version to go with your JuliaCon?

The second release candidate for Julia v1.5.0 is now available. As usual, binaries for macOS, Windows (32-, 64-bit), macOS (x86-64), FreeBSD (x86-64), glibc Linux (i686, x86-64, AArch64), and musl Linux (x86-64) at https://julialang.org/downloads, in the “upcoming release” section. Check out the NEWS file to see what will be new in 1.5.0 and the commit comparison to see what’s been included since 1.5.0-rc1.

As a release candidate, this should not be considered production-ready. Rather, it’s intended to give users a chance to try out their code with 1.5.0 prior to a full release. Note that 1.5 on Travis, AppVeyor (with Appveyor.jl) and Cirrus (with CirrusCI.jl) now points to 1.5.0-rc2.

Let us know in the issue tracker if you run into any issues. Please note that any bugs you may encounter should be posted there rather than being discussed in this thread to ensure visibility to the developers. If all goes well, we’ll move forward with a full release soon.

55 Likes

I have problems updating Julia. Does someone have a tutorial?

Generally, it’s identical to installing julia, though there are a number of different ways to install - it might be helpful if you could mention how you installed the first time (if you remember), what your OS is etc

1 Like

Shouldn’t the existence of issues like




prevent the release of a new release candidate at this stage?

At a quick glance, they don’t seem to be regressions?

I was thinking that release candidates had no known bugs, but after having read some older posts like


it seems that is not the case.

I guess that depends on which version you compare against :sweat_smile:

1 Like

rc just means there are no release blocking bugs. Is that definition circular? Yes. But no release will ever be 100% bug free, so we have to make a judgement call.

5 Likes

That is very much not the case and if we tried to achieve that there would be no more releases.

9 Likes

Note that practically all releases have outstanding issues (currently, Julia has 3k+ open issues), some of which are “bugs”. It’s just that some of these are tagged in connection with a release.

5 Likes

julia 1.5-rc docker images has been refreshed to rc2

  • glibc example:
    • docker pull julia:1.5-rc-buster
  • musl example:
    • docker pull julia:1.5-rc-alpine3.12

alpine ( musl ) example:


$ docker run -it --rm julia:1.5-rc-alpine3.12
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.5.0-rc2.0 (2020-07-27)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia> 
6 Likes

Where can one find the documentation for the release candidate? The docs website has documentation for version <= v1.4.2 and v1.6-dev, but nothing for v1.5.

1 Like

https://docs.julialang.org/en/v1.5.0-rc2.0/

4 Likes

Thank you!

Shouldn’t it be accessible from the documentation website directly? I mean it is a bit strange that one can access the v1.6 docs, which is nowhere close to release, but have to search on discourse for a link to the upcoming release docs. May I suggest including the link in the top post if it isn’t possible to make it available on the documentation website?

1 Like

Well, technically, they can access the development docs (that is, what’s on master). At present, the master branch is what’s going to become 1.6.

I agree this is a bit weird, and it might be nice to have stable, rc, and dev versions or something. Might be a bit weird during times when there’s no release candidate, or (I don’t know if this would ever happen) if there were two different release candidates, but in the first case, perhaps the rc version could just redirect to stable?

1 Like

Yea. I actually promised @mbauman to fix this a while ago so https://github.com/JuliaLang/julia/pull/36859

7 Likes

That may be somewhat confusing.

Generally I think it would make more sense to just have a convenient way of opening the local version of whatever version one is running in the browser. The docs website is great for linking to (eg in discussions here), but RCs are transient so this use case may not be applicable.

2 Likes

Maybe, though in the case where there’s no release candidate, I think stable is the most recent release candidate :man_shrugging:

Deployed! 1.5.0-rc2 is now in the version selector at https://docs.julialang.org.

9 Likes