# Julia v1.5.0-beta1 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381>\
**Category:** Announcements\
**Tags:** release\
**Created:** [May 28, 2020, 10:16pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381 "2020-05-28T22:16:25Z")\
**Posts on this page:** 20\
**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:** [May 28, 2020, 10:16pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/1 "2020-05-28T22:16:25Z")

</div>

The Julia developers are pleased to announce that Julia v1.5.0 is now in beta, and binaries for the first beta version, 1.5.0-beta1, are available now. You can get them 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 making its debut, [musl](https://en.wikipedia.org/wiki/Musl) Linux (x86-64). Check out the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.5.0-beta1/NEWS.md) to see what will be new in 1.5.0.

As a beta version, this should **not** be considered production-ready. Rather, it’s intended to give users, especially package developers, 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-beta1.

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.

Happy coding!

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [May 29, 2020, 2:15pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/2 "2020-05-29T14:15:39Z")

</div>

5 posts were split to a new topic: [Using superscript ⁻¹ as a postfix operator for inv?](https://discourse.julialang.org/t/using-superscript-as-a-postfix-operator-for-inv/40413)

---

<div class="post-metadata">

**Author:** ![tbeason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tbeason/32/15898_2.png) [@tbeason](https://discourse.julialang.org/u/tbeason)\
**Post date:** [May 28, 2020, 10:52pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/4 "2020-05-28T22:52:51Z")

</div>

Dang. I hardly had time to complain about 1.4.2

👍

---

<div class="post-metadata">

**Author:** ![vlandau](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vlandau/32/8986_2.png) [@vlandau](https://discourse.julialang.org/u/vlandau)\
**Post date:** [May 28, 2020, 11:09pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/5 "2020-05-28T23:09:09Z")

</div>

I’m getting errors in Travis during the installation step on Ubuntu

```julia
Installing Julia
0.01s$ CURL_USER_AGENT="Travis-CI $(curl --version | head -n 1)"
0.00s$ mkdir -p ~/julia
0.38s$ curl -A "$CURL_USER_AGENT" -sSf -L --retry 7 'https://julialang-s3.julialang.org/bin/linux/x64/1.5/julia-1.5-latest-linux-x86_64.tar.gz' | tar -C ~/julia -x -z --strip-components=1 -f -
curl: (22) The requested URL returned error: 404 Not Found
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
The command "curl -A "$CURL_USER_AGENT" -sSf -L --retry 7 'https://julialang-s3.julialang.org/bin/linux/x64/1.5/julia-1.5-latest-linux-x86_64.tar.gz' | tar -C ~/julia -x -z --strip-components=1 -f -" failed and exited with 2 during .

```

Presumably this is a problem on Travis’s end, or with 1.5? Tests passed for Mac.

---

<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:** [May 28, 2020, 11:12pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/6 "2020-05-28T23:12:09Z")

</div>

> [@vlandau](#):
>
> Presumably this is a problem on Travis’s end

I believe so, since `curl`ing that works for me locally. Sometimes their caching can be a little odd. You could give it a bit then try again.

---

<div class="post-metadata">

**Author:** ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Post date:** [May 28, 2020, 11:43pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/7 "2020-05-28T23:43:37Z")

</div>

Might be an issue with the special caching that we do on Travis and other CI services. @staticfloat

---

<div class="post-metadata">

**Author:** ![NHDaly](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nhdaly/32/1413_2.png) [@NHDaly](https://discourse.julialang.org/u/NHDaly)\
**Post date:** [May 29, 2020, 12:46am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/8 "2020-05-29T00:46:40Z")

</div>

Is this the equivalent of `-rc1`? We’re using `beta` now? That’s probably more widely understood than rc, so makes sense to me 🙂 👍

---

<div class="post-metadata">

**Author:** ![dpsanders](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dpsanders/32/3573_2.png) [@dpsanders](https://discourse.julialang.org/u/dpsanders)\
**Post date:** [May 29, 2020, 1:06am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/9 "2020-05-29T01:06:51Z")

</div>

Hasn’t there always been a `beta` prior to `rc`?

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [May 29, 2020, 1:29am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/10 "2020-05-29T01:29:56Z")

</div>

I don’t know if I’m just lucky, but all the nightly versions recently have been really solid. All would just work!

Bang up job, guys! Thank you very much.

---

<div class="post-metadata">

**Author:** ![NHDaly](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nhdaly/32/1413_2.png) [@NHDaly](https://discourse.julialang.org/u/NHDaly)\
**Post date:** [May 29, 2020, 1:31am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/11 "2020-05-29T01:31:48Z")

</div>

Ah, sorry, i couldn’t remember. 😅 Might’ve been wrong about that

---

<div class="post-metadata">

**Author:** ![xiaodai](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xiaodai/32/15937_2.png) [@xiaodai](https://discourse.julialang.org/u/xiaodai)\
**Post date:** [May 29, 2020, 3:07am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/13 "2020-05-29T03:07:07Z")

</div>

peak mem usage reduced. Very nice!

---

<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:** [May 29, 2020, 3:34am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/14 "2020-05-29T03:34:55Z")

</div>

and now - the `docker` image is ready ! 🐳 :julia:  
see the latest tags : [Docker](https://hub.docker.com/_/julia?tab=tags)

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

```

---

<div class="post-metadata">

**Author:** ![staticfloat](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/staticfloat/32/34_2.png) [@staticfloat](https://discourse.julialang.org/u/staticfloat)\
**Post date:** [May 29, 2020, 5:21am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/15 "2020-05-29T05:21:01Z")

</div>

Indeed, in general you’re going to need to wait a few hours before CI services in various cloud regions will have the file ready. That may not always be true, but for now it is, because of how we copy from the global S3 bucket that a standard user would download from, to the specialized datacenter-local caches we maintain for each cloud provider.

---

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [May 29, 2020, 5:45am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/16 "2020-05-29T05:45:52Z")

</div>

The first official binaries where the current REPL task is the root `Task`.

```julia
julia> Base.roottask == current_task()
true

```

---

<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:** [May 29, 2020, 6:54am UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/17 "2020-05-29T06:54:21Z")

</div>

> [@NHDaly](#):
>
> Is this the equivalent of `-rc1` ? We’re using `beta` now? That’s probably more widely understood than rc, so makes sense to me

Not really equivalent. The RCs typically (except 1.4.0 RC1 IIRC) have had more thorough “quality control” than this beta. The choice to release an early beta is to get a longer testing time, even if some of that testing time is on a version of 1.5 that is a bit polished.

> [@dpsanders](#):
>
> Hasn’t there always been a `beta` prior to `rc` ?

Don’t think so. I think we had an alpha for 1.3 (or was that 1.4?).

---

<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:** [May 29, 2020, 12:21pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/20 "2020-05-29T12:21:15Z")

</div>

> **Ooops... ignore me!**
>
> Stefan had said that 1.5 is likely to become the new LTS. Makes sense to have a longer testing phase, if that’s a possibility.

---

<div class="post-metadata">

**Author:** ![oschulz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oschulz/32/2998_2.png) [@oschulz](https://discourse.julialang.org/u/oschulz)\
**Post date:** [May 29, 2020, 1:06pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/21 "2020-05-29T13:06:17Z")

</div>

The new inline allocation of structs with pointers in v1.5 is awesome:

[https://github.com/JuliaArrays/UnsafeArrays.jl/issues/8](https://github.com/JuliaArrays/UnsafeArrays.jl/issues/8)

---

<div class="post-metadata">

**Author:** ![heliosdrm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/heliosdrm/32/3851_2.png) [@heliosdrm](https://discourse.julialang.org/u/heliosdrm)\
**Post date:** [May 29, 2020, 1:16pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/22 "2020-05-29T13:16:57Z")

</div>

Not really; he recently said that **1.6** is likely to become the next LTS:

> [@What are the guarantees of LTS Julia versions?](https://discourse.julialang.org/t/what-are-the-guarantees-of-lts-julia-versions/39572/6):
>
> In addition to what I wrote in that post, it’s looking very likely that 1.6 will become the new LTS. Supporting 1.0 is starting to get fairly onerous for packages and for making new Julia releases to what is now a very old branch. In particular, the package manager has added enough new features that continuing to support both 1.0 and 1.6+ would be increasingly tricky.

---

<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:** [May 29, 2020, 1:25pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/24 "2020-05-29T13:25:39Z")

</div>

Ahh - good catch. Sorry for the misinformation!

---

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [June 21, 2020, 9:54pm UTC](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381/25 "2020-06-21T21:54:02Z")

</div>

Shouldn’t then be 1.6 called 2.0? Having a 1.6 as LTR is a bit confusing I feel…

[Next page](https://discourse.julialang.org/t/julia-v1-5-0-beta1-is-now-available/40381.md?page=2)