# Julia v1.5.0-rc1 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164>\
**Category:** Announcements\
**Tags:** release\
**Created:** [June 27, 2020, 7:04pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164 "2020-06-27T19:04:54Z")\
**Posts on this page:** 7\
**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:** [June 27, 2020, 7:04pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164/1 "2020-06-27T19:04:54Z")

</div>

The Julia developers are pleased to announce that the first release candidate for Julia v1.5.0 is now available. Binaries for the release candidate, 1.5.0-rc1, can be found at [Download Julia](https://julialang.org/downloads) in the “upcoming release” section for macOS, FreeBSD (x86-64), Windows (32-, 64-bit), glibc Linux (i686, x86-64, AArch64), and [musl](https://en.wikipedia.org/wiki/Musl) Linux (x86-64). Check out the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.5.0-rc1/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-beta1...v1.5.0-rc1) to see what’s been included since 1.5.0-beta1.

As a release candidate, this should **not** be considered production-ready. Rather, it’s intended to give users a chance to try our 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-rc1.

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.

Happy coding!

P.S. A note to Linux users: Not sure whether you want glibc or musl binaries? You probably want glibc; most distributions use that as their libc and those that do not make it clear.

---

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [June 28, 2020, 7:17am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164/2 "2020-06-28T07:17:57Z")

</div>

I have a few questions that in principle apply not only to 1.5 release, but they are closely related with some of the current `NEWS` points.

Is there any vision/plans that at some point in the future:

- There are fewer whitespace-sensitive stuctures, most notably in array construction?  
`Attention has to be paid in macros and matrix constructors, which are whitespace sensitive, because expressions like [a ±b] now get parsed as [a ±(b)] instead of [±(a, b)]`  
in the release notes reminded me about this.

- Currying is more general and consistent? E.g. now `contains(a, b) == contains(b)(a)` looks pretty surprising, even though I see why it was done this way.

- `dims` arguments in `Base` are handled in a general way that doesn’t require individual functions to implement it? E.g. in the NEWS: `count now accepts the dims keyword.` It would make sense for all aggregations to automatically work with `dims`, so that specific implementations are there only to get the absolute best performance.

---

<div class="post-metadata">

**Author:** ![lungben](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lungben/32/12314_2.png) [@lungben](https://discourse.julialang.org/u/lungben)\
**Post date:** [June 28, 2020, 8:01am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164/3 "2020-06-28T08:01:21Z")

</div>

> [@ararslan](#):
>
> Not sure whether you want glibc or musl binaries?

Could we have an official Julia Docker image based on Alpine Linux using the new musl binaries (in addition to the Debian based ones)? This would probably give significantly smaller image sizes (currently 450 MB for Debian based Julia).

---

<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:** [June 28, 2020, 8:17am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164/4 "2020-06-28T08:17:15Z")

</div>

That’s probably a question to ask (or a pull request to open) in [https://github.com/docker-library/julia](https://github.com/docker-library/julia)

---

<div class="post-metadata">

**Author:** ![lungben](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lungben/32/12314_2.png) [@lungben](https://discourse.julialang.org/u/lungben)\
**Post date:** [June 28, 2020, 7:07pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164/5 "2020-06-28T19:07:22Z")

</div>

Thanks for the link, PR is created:  
[https://github.com/docker-library/julia/pull/47](https://github.com/docker-library/julia/pull/47)

---

<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:** [June 30, 2020, 2:31am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164/6 "2020-06-30T02:31:04Z")

</div>

the `Julia 1.5.0-rc1` docker image is ready

- [Docker Hub](https://hub.docker.com/_/julia?tab=tags&page=1&name=1.5.0-rc1)

```bash
$ docker pull julia:1.5.0-rc1
1.5.0-rc1: Pulling from library/julia
Digest: sha256:2c3cbc2420e96165ed78c1daca98de9dd7152892e9c4db1f4ab8e5dd38b5e786
Status: Downloaded newer image for julia:1.5.0-rc1
docker.io/library/julia:1.5.0-rc1

$ docker run -it --rm julia:1.5.0-rc1 
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 1.5.0-rc1.0 (2020-06-26)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |

julia> 

```

---

<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 1, 2020, 12:48am UTC](https://discourse.julialang.org/t/julia-v1-5-0-rc1-is-now-available/42164/7 "2020-07-01T00:48:50Z")

</div>

Thanks for the PR !  
As I see - now: the **julia:1.5.0-rc1-alpine3.12** (musl) docker image is ready to test.

```bash
$ docker pull julia:1.5.0-rc1-alpine3.12
1.5.0-rc1-alpine3.12: Pulling from library/julia
df20fa9351a1: Already exists 
2ec200ff2b9e: Pull complete 
Digest: sha256:c0c8976a24c4e4de3d766932c6e4a580f230bbb9b2d8f023b1ace6e933a821d6
Status: Downloaded newer image for julia:1.5.0-rc1-alpine3.12
docker.io/library/julia:1.5.0-rc1-alpine3.12

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

julia> versioninfo()
Julia Version 1.5.0-rc1.0
Commit 24f033c951 (2020-06-26 20:13 UTC)
Platform Info:
  OS: Linux (x86_64-linux-musl)
  CPU: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-9.0.1 (ORCJIT, skylake)
Environment:
  JULIA_PATH = /usr/local/julia
  JULIA_GPG = 3673DF529D9049477F76B37566E3C7DC03D6E495
  JULIA_VERSION = 1.5.0-rc1

julia> 

```