# Julia v1.3.0-rc1 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673>\
**Category:** Announcements\
**Tags:** release\
**Created:** [August 18, 2019, 7:04am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673 "2019-08-18T07:04:02Z")\
**Posts on this page:** 12\
**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:** [August 18, 2019, 7:04am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/1 "2019-08-18T07:04:02Z")

</div>

The first release candidate for Julia v1.3.0 is here! Get binaries for Linux, macOS, Windows, and FreeBSD at [Download Julia](https://julialang.org/downloads) and check out the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.3.0-rc1/NEWS.md) for v1.3.0-rc1 to see what will be new in 1.3. You can also view the commit comparison with the previously released 1.3.0-alpha [here](https://github.com/JuliaLang/julia/compare/v1.3.0-alpha...v1.3.0-rc1).

As a release candidate, this should **not** be considered production-ready; it’s intended to give users a chance to try out their code with 1.3.0 prior to a full release. Note that 1.3 on Travis, AppVeyor (with [Appveyor.jl](https://github.com/JuliaCI/Appveyor.jl)), and Cirrus CI (with [CirrusCI.jl](https://github.com/ararslan/CirrusCI.jl)) now points to 1.3.0-rc1 rather than 1.3.0-alpha.

Don’t worry, even though 1.3 is now in the release candidate stage doesn’t mean we’ve forgotten about 1.2; that should be available [very soon](https://discourse.julialang.org/t/julia-v1-2-0-rc3-is-now-available/27480).

As usual, let us know in the [issue tracker](https://github.com/JuliaLang/julia/issues) if you run into any issues.

---

<div class="post-metadata">

**Author:** ![johnh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johnh/32/3615_2.png) [@johnh](https://discourse.julialang.org/u/johnh)\
**Post date:** [August 18, 2019, 7:13am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/2 "2019-08-18T07:13:28Z")

</div>

Installed and running already. I like living on the edge!

---

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [August 18, 2019, 7:17am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/3 "2019-08-18T07:17:25Z")

</div>

Note that #32918 (artifacts) in the News.md is missing a link.

---

<div class="post-metadata">

**Author:** ![hyper0x](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/hyper0x/32/9831_2.png) [@hyper0x](https://discourse.julialang.org/u/hyper0x)\
**Post date:** [August 18, 2019, 8:15am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/4 "2019-08-18T08:15:03Z")

</div>

Does this mean that the release dates of 1.2.0 and 1.3.0 will be very close? Is there any special reason for this? I don’t know Julia’s history.

---

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [August 18, 2019, 8:22am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/5 "2019-08-18T08:22:45Z")

</div>

1.2.0 should still be out first. The reason for 1.3.0 is that it introduces new parallel paradigm, so people are very hyped (same for the devs)

---

<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:** [August 18, 2019, 8:26am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/6 "2019-08-18T08:26:18Z")

</div>

> [@hyper0x](#):
>
> Does this mean that the release dates of 1.2.0 and 1.3.0 will be very close? Is there any special reason for this?

No, 1.2 is almost completely stabilized and will be released soon while 1.3 just got branched and is likely months away to be released.

---

<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:** [August 18, 2019, 9:14am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/7 "2019-08-18T09:14:10Z")

</div>

I just want to track 1.3 through its release cycle, is it enough to just

```nohighlight
git checkout release-1.3 # once
git pull && make # for updates

```

?

---

<div class="post-metadata">

**Author:** ![hyper0x](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/hyper0x/32/9831_2.png) [@hyper0x](https://discourse.julialang.org/u/hyper0x)\
**Post date:** [August 18, 2019, 10:13am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/8 "2019-08-18T10:13:33Z")

</div>

> [@kristoffer.carlsson](#):
>
> No, 1.2 is almost completely stabilized and will be released soon while 1.3 just got branched and is likely months away to be released.

I see, thank you.

---

<div class="post-metadata">

**Author:** ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)\
**Post date:** [August 18, 2019, 2:50pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/9 "2019-08-18T14:50:15Z")

</div>

For those that want to try it out, Atom/Juno is currently broken for Julia `v"1.3.0-rc1"`.  
[https://github.com/JuliaLang/julia/issues/32951](https://github.com/JuliaLang/julia/issues/32951)

---

<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:** [August 18, 2019, 5:19pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/10 "2019-08-18T17:19:13Z")

</div>

FYI folks I jumped the gun a bit with this release candidate; please consider this more of a beta. We’ll continue to iterate with RC versions but this was a bit premature, so the _next_ release candidate will be more like a true RC. My apologies!

---

<div class="post-metadata">

**Author:** ![dlfivefifty](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dlfivefifty/32/1959_2.png) [@dlfivefifty](https://discourse.julialang.org/u/dlfivefifty)\
**Post date:** [September 1, 2019, 10:10pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/11 "2019-09-01T22:10:11Z")

</div>

FWIW the whole ApproxFun system passes tests on rc1 without a single segfault 🎉 in the past this usually only occurred in the last or penultimate release candidate of any julia version. Though I suppose it’s single threaded so not really testing the main contributions of 1.3.

In any case, I’m hoping “more of a beta” means “really buggy”, not “we’re going to make big changes that introduce new bugs that breaK in ApproxFun

---

<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:** [September 2, 2019, 7:14am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/12 "2019-09-02T07:14:57Z")

</div>

> [@dlfivefifty](#):
>
> I’m hoping “more of a beta” means “really buggy”, not “we’re going to make big changes that introduce new bugs that breaK in ApproxFun

Feature freeze is still in effect. For this RC, the “problem” was just that we didn’t run the normal stabilisation checks that we usually do before an RC (PkgEval + Nanosoldier). For those that want to follow along and maybe help out, the PkgEval process for RC2 is at [https://github.com/JuliaLang/julia/pull/32973#issuecomment-525447222](https://github.com/JuliaLang/julia/pull/32973#issuecomment-525447222).