# Julia v1.5.0-rc2 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789>\
**Category:** Announcements\
**Tags:** release\
**Created:** [July 27, 2020, 8:09pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789 "2020-07-27T20:09:21Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)\
**Post date:** [July 27, 2020, 8:09pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/1 "2020-07-27T20:09:21Z")

</div>

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](https://en.wikipedia.org/wiki/Musl) Linux (x86-64) at [Download Julia](https://julialang.org/downloads), in the “upcoming release” section. Check out the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.5.0-rc2/NEWS.md) to see what will be new in 1.5.0 and the [commit comparison](https://github.com/JuliaLang/julia/compare/v1.5.0-rc1...v1.5.0-rc2) 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](https://github.com/JuliaCI/Appveyor.jl)) and Cirrus (with [CirrusCI.jl](https://github.com/ararslan/CirrusCI.jl)) now points to 1.5.0-rc2.

Let us know in the [issue tracker](https://github.com/JuliaLang/julia/issues) 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.

---

<div class="post-metadata">

**Author:** ![Norbert-droid](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/norbert-droid/32/20364_2.png) [@Norbert-droid](https://discourse.julialang.org/u/Norbert-droid)\
**Post date:** [July 28, 2020, 12:02am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/2 "2020-07-28T00:02:18Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [July 28, 2020, 12:28am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/3 "2020-07-28T00:28:53Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![baggepinnen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/baggepinnen/32/693_2.png) [@baggepinnen](https://discourse.julialang.org/u/baggepinnen)\
**Post date:** [July 28, 2020, 7:04am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/4 "2020-07-28T07:04:56Z")

</div>

Shouldn’t the existence of issues like  
[https://github.com/JuliaLang/julia/issues/36544](https://github.com/JuliaLang/julia/issues/36544)  
[https://github.com/JuliaLang/julia/issues/36804](https://github.com/JuliaLang/julia/issues/36804)  
[https://github.com/JuliaLang/julia/issues/36185](https://github.com/JuliaLang/julia/issues/36185)  
prevent the release of a new release candidate at this stage?

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [July 28, 2020, 7:31am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/5 "2020-07-28T07:31:24Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![baggepinnen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/baggepinnen/32/693_2.png) [@baggepinnen](https://discourse.julialang.org/u/baggepinnen)\
**Post date:** [July 28, 2020, 7:45am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/6 "2020-07-28T07:45:59Z")

</div>

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

> [@It is time... for Julia v0.7.0-rc2](https://discourse.julialang.org/t/it-is-time-for-julia-v0-7-0-rc2/12868/6):
>
> Assuming no bugs, we thought it was ready. But there were bugs, so it was not and we fixed them. Also, we will sometimes do an rc even with minor known issues to be addressed in the next rc to give people a chance to get the rest of the fixes they may be waiting on. This is all standard software development practice. It’s also a signal for the kind of changes that may go into the release. E.g. at this point we’re no longer gonna add any deprecations (with the usual disclaimers that common sense…

it seems that is not the case.

> [@giordano](#):
>
> they don’t seem to be regressions?

I guess that depends on which version you compare against 😅

---

<div class="post-metadata">

**Author:** ![Keno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/keno/32/285_2.png) [@Keno](https://discourse.julialang.org/u/Keno)\
**Post date:** [July 28, 2020, 7:47am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/8 "2020-07-28T07:47:28Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [July 28, 2020, 9:00am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/9 "2020-07-28T09:00:40Z")

</div>

> [@baggepinnen](#):
>
> I was thinking that release candidates had no known bugs

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

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [July 28, 2020, 9:06am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/10 "2020-07-28T09:06:08Z")

</div>

> [@baggepinnen](#):
>
> release candidates had no known bugs

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.

---

<div class="post-metadata">

**Author:** ![ImreSamu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/imresamu/32/20677_2.png) [@ImreSamu](https://discourse.julialang.org/u/ImreSamu)\
**Post date:** [July 29, 2020, 1:54am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/11 "2020-07-29T01:54:51Z")

</div>

[julia 1.5-rc docker images](https://hub.docker.com/_/julia?tab=tags&page=1&name=1.5-rc) 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:

```julia

$ 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> 

```

---

<div class="post-metadata">

**Author:** ![scimas](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@scimas](https://discourse.julialang.org/u/scimas)\
**Post date:** [July 30, 2020, 3:32pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/12 "2020-07-30T15:32:34Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [July 30, 2020, 3:49pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/13 "2020-07-30T15:49:15Z")

</div>

[https://docs.julialang.org/en/v1.5.0-rc2.0/](https://docs.julialang.org/en/v1.5.0-rc2.0/)

---

<div class="post-metadata">

**Author:** ![scimas](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@scimas](https://discourse.julialang.org/u/scimas)\
**Post date:** [July 30, 2020, 4:04pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/14 "2020-07-30T16:04:32Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [July 30, 2020, 4:55pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/15 "2020-07-30T16:55:37Z")

</div>

> [@scimas](#):
>
> I mean it is a bit strange that one can access the v1.6 docs

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`?

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [July 30, 2020, 5:56pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/16 "2020-07-30T17:56:49Z")

</div>

> [@scimas](#):
>
> Shouldn’t it be accessible from the documentation website directly?

Yea. I actually promised @mbauman to fix this a while ago so [Better deployment of rc docs by fredrikekre · Pull Request #36859 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/pull/36859)

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [July 31, 2020, 7:42am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/17 "2020-07-31T07:42:07Z")

</div>

> [@kevbonham](#):
>
> perhaps the `rc` version could just redirect to `stable` ?

That may be somewhat confusing.

> [@scimas](#):
>
> Shouldn’t it be accessible from the documentation website directly?

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.

---

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [July 31, 2020, 2:28pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/18 "2020-07-31T14:28:12Z")

</div>

> [@Tamas\_Papp](#):
>
> That may be somewhat confusing.

Maybe, though in the case where there’s no release candidate, I think `stable` is the most recent release candidate 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [July 31, 2020, 3:37pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc2-is-now-available/43789/19 "2020-07-31T15:37:07Z")

</div>

Deployed! `1.5.0-rc2` is now in the version selector at [https://docs.julialang.org](https://docs.julialang.org).