# Julia v1.2.0-rc2 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-2-0-rc2-is-now-available/26170>\
**Category:** Announcements\
**Tags:** release\
**Created:** [July 9, 2019, 5:04am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc2-is-now-available/26170 "2019-07-09T05:04:38Z")\
**Posts on this page:** 5\
**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 9, 2019, 5:04am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc2-is-now-available/26170/1 "2019-07-09T05:04:38Z")

</div>

The second release candidate for Julia v1.2.0 is here! You can get binaries for all tier 1 platforms from the “upcoming release” section of [Download Julia](https://julialang.org/downloads). See the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.2.0-rc2/NEWS.md) for v1.2.0-rc2 to get a taste for what will be new in 1.2. You can also see the commit comparison with the first 1.2 release candidate [here](https://github.com/JuliaLang/julia/compare/v1.2.0-rc1...v1.2.0-rc2).

As a release candidate, this should **not** be considered production-ready; it’s intended to give users, especially package developers, a chance to test their code with v1.2.0 before the full release. Note that 1.2 on Travis, AppVeyor, and Cirrus now points to v1.2.0-rc2, so you can test with this release on CI. If you run into any issues, let us know in the [issue tracker](https://github.com/JuliaLang/julia/issues).

Enjoy!

---

<div class="post-metadata">

**Author:** ![Gnimuc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gnimuc/32/2194_2.png) [@Gnimuc](https://discourse.julialang.org/u/Gnimuc)\
**Post date:** [July 9, 2019, 10:21am UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc2-is-now-available/26170/3 "2019-07-09T10:21:04Z")

</div>

I’m wondering whether these binaries were built using LLVMBuilder or not. It would be great if Julia 1.2 could be one-to-one mapped to the LLVMBuilder releases.

---

<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 9, 2019, 4:17pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc2-is-now-available/26170/4 "2019-07-09T16:17:51Z")

</div>

> [@Gnimuc](#):
>
> I’m wondering whether these binaries were built using LLVMBuilder or not

They were indeed. You can see the full list of options passed to the build on the builds site, for example the “flags” entry in the “Build Properties” tab of [https://build.julialang.org/#/builders/53/builds/3988](https://build.julialang.org/#/builders/53/builds/3988). In particular note that `USE_BINARYBUILDER=1` is being passed in.

---

<div class="post-metadata">

**Author:** ![computerhoncho](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/computerhoncho/32/8949_2.png) [@computerhoncho](https://discourse.julialang.org/u/computerhoncho)\
**Post date:** [August 16, 2019, 1:07pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc2-is-now-available/26170/5 "2019-08-16T13:07:23Z")

</div>

All:

Does this version work with Windows 10 or different distros of Linux ??

Please advise.

Many thanks,

Newbie to Julia, Mason Yu Jr.

---

<div class="post-metadata">

**Author:** ![Karajan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/karajan/32/8545_2.png) [@Karajan](https://discourse.julialang.org/u/Karajan)\
**Post date:** [August 16, 2019, 1:15pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-rc2-is-now-available/26170/6 "2019-08-16T13:15:40Z")

</div>

It should work both on (all common) Linux and Windows. But note that there is already a [v1.2.0-rc3](https://discourse.julialang.org/t/julia-v1-2-0-rc3-is-now-available/27480) out; you can find all versions for all OS on the download page posted above.
