# Julia v1.0-rc1 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008>\
**Category:** Announcements\
**Tags:** release\
**Created:** [August 7, 2018, 11:47pm UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008 "2018-08-07T23:47:21Z")\
**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:** [August 7, 2018, 11:47pm UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/1 "2018-08-07T23:47:21Z")

</div>

The Julia developers are incredibly pleased to announce that v1.0.0-rc1, the first release candidate for the first major release of Julia, is now available! Binaries for the release candidate are available for Linux (i686, x86-64), Windows (32-, 64-bit), macOS, and FreeBSD (x86-64) at [Download Julia](https://julialang.org/downloads).

As a prerelease, 1.0-rc1 should not be considered production-ready. It’s intended to give developers a chance to get ready for the release of 1.0 by trying it out and testing for issues. Most users should continue to use the latest release (0.6.4 at the time of writing) until 1.0 is fully released. Please report any issues to [Issues · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues).

In case you’re wondering, the primary difference between 0.7 and 1.0 is the removal of deprecations. Unsurprisingly this has proven to be rather breaking, and we’re all working hard to mitigate the issues. If you’re looking for an easy way to contribute to the Julia package ecosystem, fixing deprecations on 0.7 is a great way to start.

We hope you’re as excited about this as we are, and we hope you’ll download it and take it for a spin!

---

<div class="post-metadata">

**Author:** ![js135005](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/js135005/32/8219_2.png) [@js135005](https://discourse.julialang.org/u/js135005)\
**Post date:** [August 7, 2018, 11:50pm UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/2 "2018-08-07T23:50:37Z")

</div>

It’s not posted on the download page yet.

Edit: It’s there now and 64-bit Windows version works at first glance.

---

<div class="post-metadata">

**Author:** ![davidbp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidbp/32/463_2.png) [@davidbp](https://discourse.julialang.org/u/davidbp)\
**Post date:** [August 7, 2018, 11:56pm UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/3 "2018-08-07T23:56:07Z")

</div>

The mac url does not work!

---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [August 8, 2018, 12:17am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/4 "2018-08-08T00:17:07Z")

</div>

Works for linux

---

<div class="post-metadata">

**Author:** ![non-Jedi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/non-jedi/32/3645_2.png) [@non-Jedi](https://discourse.julialang.org/u/non-Jedi)\
**Post date:** [August 8, 2018, 12:35am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/5 "2018-08-08T00:35:49Z")

</div>

I know I read somewhere that work was being done on having Julia use a more up-to-date LLVM, and I left with the impression that it’d switch before 1.0. The README still says 3.9 though; is the plan to switch some time later on a minor version? LLVM 3.9 is currently being packaged on my system solely for Julia, and it’d be really nice to eliminate that.

---

<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:** [August 8, 2018, 12:40am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/6 "2018-08-08T00:40:15Z")

</div>

The current LLVM version is 6.0. Good catch on the README! Would you like to make a Pull Request to fix it? You can do it by navigating to

> <https://github.com/JuliaLang/julia/blob/master/README.md>

and clicking the pencil icon.

---

<div class="post-metadata">

**Author:** ![una-dinosauria](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/una-dinosauria/32/2077_2.png) [@una-dinosauria](https://discourse.julialang.org/u/una-dinosauria)\
**Post date:** [August 8, 2018, 1:36am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/7 "2018-08-08T01:36:41Z")

</div>

Can confirm that mac URL is not working

---

<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 8, 2018, 4:47am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/8 "2018-08-08T04:47:30Z")

</div>

> [@ararslan](#):
>
> In case you’re wondering, the primary difference between 0.7 and 1.0 is the removal of deprecations.

I understood this, but for some reason thought that there would be a time period between the v0.7 and v1.0 releases, to allow the packages to catch up (surprisingly many, in fact, are not ready for v0.7 at the moment).

---

<div class="post-metadata">

**Author:** ![saschatimme](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/saschatimme/32/10313_2.png) [@saschatimme](https://discourse.julialang.org/u/saschatimme)\
**Post date:** [August 8, 2018, 4:53am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/9 "2018-08-08T04:53:36Z")

</div>

I noticed that the default test script on travis-ci for 1.0.0-rc1 is broken. Where is the best place to report this? ([Here](https://travis-ci.org/JuliaAlgebra/TypedPolynomials.jl/jobs/413418615#L1) is an example log).

---

<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 8, 2018, 5:39am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/10 "2018-08-08T05:39:48Z")

</div>

The Windows download is working!  
Yaaay!

VideoIO package fails miserably when I pkg add it… will report to VideoIO though!

---

<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 8, 2018, 5:49am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/11 "2018-08-08T05:49:04Z")

</div>

This is not looking good with Images.jl  
If this is an Images problem I will open an issue over there. Please tell me that Images is .0 compatible - it is a pretty fundamental package.  
Julia Windows 10 1.0-rc1

julia\> using Images  
[Info: Precompiling Images [916415d5-f1e6-5110-898d-aaa5f9f070e0]  
WARNING: could not import Base.atan2 into Images  
WARNING: could not import Base.ctranspose into Images  
WARNING: could not import Base.fft into Images  
WARNING: could not import Base.ifft into Images  
WARNING: could not import Base.linearindexing into Images  
WARNING: could not import Base.mimewritable into Images  
WARNING: could not import Base.showcompact into Images  
WARNING: could not import Base.squeeze into Images  
WARNING: could not import Base.reducedim into StaticArrays  
WARNING: could not import Base.mapreducedim into StaticArrays  
WARNING: could not import LinearAlgebra.vecdot into StaticArrays  
WARNING: could not import LinearAlgebra.svdfact into StaticArrays  
WARNING: could not import Base.linspace into Colors

---

<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 8, 2018, 6:35am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/12 "2018-08-08T06:35:46Z")

</div>

Very sorry about the macOS binaries, folks! They were inadvertently uploaded out a level in the file tree. They’ve been fixed now, and so the Mac links should now work. For convenience:

[https://julialang-s3.julialang.org/bin/mac/x64/1.0/julia-1.0.0-rc1-mac64.dmg](https://julialang-s3.julialang.org/bin/mac/x64/1.0/julia-1.0.0-rc1-mac64.dmg)

---

<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:** [August 8, 2018, 6:54am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/13 "2018-08-08T06:54:23Z")

</div>

What is the issue? Do you get any actual errors?

---

<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 8, 2018, 7:36am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/14 "2018-08-08T07:36:19Z")

</div>

Regarding Images.jl yes - I have cut and pasted the errors below.

Regarding VideoIO - this is a GTK problem and I have seen similar in the past. Issue opened with VideoIO on GitHub

WARNING: could not import Base.showcompact into Images  
WARNING: could not import Base.squeeze into Images  
ERROR: LoadError: LoadError: UndefVarError: info not defined  
Stacktrace:  
[1] getproperty(::Module, ::Symbol) at .\sysimg.jl:13  
[2] top-level scope at none:0  
[3] include at .\boot.jl:317 [inlined]  
[4] include\_relative(::Module, ::String) at .\loading.jl:1038  
[5] include at .\sysimg.jl:29 [inlined]  
[6] include(::String) at C:\Users\hearn.julia\packages\FileIO\fuH3F\src\FileIO.jl:3  
[7] top-level scope at none:0  
[8] include at .\boot.jl:317 [inlined]  
[9] include\_relative(::Module, ::String) at .\loading.jl:1038  
[10] include(::Module, ::String) at .\sysimg.jl:29  
[11] top-level scope at none:2  
[12] eval at .\boot.jl:319 [inlined]  
[13] eval(::Expr) at .\client.jl:389  
[14] top-level scope at .\none:3  
in expression starting at C:\Users\hearn.julia\packages\FileIO\fuH3F\src\query.jl:158  
in expression starting at C:\Users\hearn.julia\packages\FileIO\fuH3F\src\FileIO.jl:32  
ERROR: LoadError: Failed to precompile FileIO [5789e2e9-d7fb-5bc7-8068-2c6fae9b9549] to C:\Users\hearn.julia\compiled\v1.0\FileIO\6iKRU.ji.  
Stacktrace:  
[1] error(::String) at .\error.jl:33  
[2] macro expansion at .\logging.jl:313 [inlined]  
[3] compilecache(::Base.PkgId, ::String) at .\loading.jl:1184  
[4] \_require(::Base.PkgId) at .\logging.jl:311  
[5] require(::Base.PkgId) at .\loading.jl:852  
[6] macro expansion at .\logging.jl:311 [inlined]  
[7] require(::Module, ::Symbol) at .\loading.jl:834  
[8] include at .\boot.jl:317 [inlined]  
[9] include\_relative(::Module, ::String) at .\loading.jl:1038  
[10] include(::Module, ::String) at .\sysimg.jl:29  
[11] top-level scope at none:2  
[12] eval at .\boot.jl:319 [inlined]  
[13] eval(::Expr) at .\client.jl:389  
[14] top-level scope at .\none:3  
in expression starting at C:\Users\hearn.julia\packages\Images\HB5LL\src\Images.jl:29  
ERROR: Failed to precompile Images [916415d5-f1e6-5110-898d-aaa5f9f070e0] to C:\Users\hearn.julia\compiled\v1.0\Images\H8Vxc.ji.  
Stacktrace:  
[1] error(::String) at .\error.jl:33  
[2] macro expansion at .\logging.jl:313 [inlined]  
[3] compilecache(::Base.PkgId, ::String) at .\loading.jl:1184  
[4] \_require(::Base.PkgId) at .\logging.jl:311  
[5] require(::Base.PkgId) at .\loading.jl:852  
[6] macro expansion at .\logging.jl:311 [inlined]  
[7] require(::Module, ::Symbol) at .\loading.jl:834

julia\>

---

<div class="post-metadata">

**Author:** ![tobias.knopp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tobias.knopp/32/7551_2.png) [@tobias.knopp](https://discourse.julialang.org/u/tobias.knopp)\
**Post date:** [August 8, 2018, 7:45am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/15 "2018-08-08T07:45:18Z")

</div>

Gtk.jl still does not work on 0.7 but there is a branch with quite some progress:

[https://github.com/JuliaGraphics/Gtk.jl/pull/331#issuecomment-410829017](https://github.com/JuliaGraphics/Gtk.jl/pull/331#issuecomment-410829017)

Unfortunately there is a StackOverFlow Error which I have not been able to track down. Help is appreciated.

---

<div class="post-metadata">

**Author:** ![tobias.knopp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tobias.knopp/32/7551_2.png) [@tobias.knopp](https://discourse.julialang.org/u/tobias.knopp)\
**Post date:** [August 8, 2018, 8:01am UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/16 "2018-08-08T08:01:10Z")

</div>

> [@Tamas\_Papp](#):
>
> I understood this, but for some reason thought that there would be a time period between the v0.7 and v1.0 releases, to allow the packages to catch up (surprisingly many, in fact, are not ready for v0.7 at the moment).

I thought that as well but core devs apparently want to release them close together:

> <https://github.com/JuliaLang/julia/pull/28489>
>
> To be merged first:
> 
> \- \[x\] #28488: Deprecations
> \- \[x\] #28486: Deprecations an…d fix \`@inferred\` macro to handle broadcast syntax.
> \- \[x\] #28485: GC lowering
> \- \[x\] #28482: Underlines in command printing
> \- \[x\] #28480: Remove some linear algebra checks
> \- \[x\] #28479: Deprecations
> \- \[x\] #28453: Stack traces
> 
> As usual, add and subtract as necessary.

I think for Julia adaptors it is a very bad experience when 1.0 is released but the package ecosystem is not ready. Further I do not see any rush. When 0.7 is available we all can use it as if it were 1.0. Just remove the deprecation warnings and they are the same. Why not have a positive press release with most packages working for 1.0?

One crucial aspect is that the migration from 0.6 to 0.7/1.0 is not very easy. Its like Python2 to Python3. I have various code where there is no solution for in 0.7 that worked fine in 0.6. Just as an instance mmap does not work anymore in many cases ([mmap with arbitrary offsets no more allowed · Issue #28424 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues/28424)) and there is no real solution to that. A workaround with `reinterpret` works but is slow.

---

<div class="post-metadata">

**Author:** ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)\
**Post date:** [August 8, 2018, 12:02pm UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/17 "2018-08-08T12:02:07Z")

</div>

> [@tobias.knopp](#):
>
> I think for Julia adaptors it is a very bad experience when 1.0 is released but the package ecosystem is not ready

I 100% agree with that.  
I think there are a numer of packages (Distributions, DataFrames, PyCall, simply the popular ones on pulse) which should work flawlessly before releasing 1.0.

---

<div class="post-metadata">

**Author:** ![bkamins](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bkamins/32/208538_2.png) [@bkamins](https://discourse.julialang.org/u/bkamins)\
**Post date:** [August 8, 2018, 1:20pm UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/18 "2018-08-08T13:20:38Z")

</div>

> [@bernhard](#):
>
> DataFrames

`DataFrames` version 0.13 (released yesterday - thanks to @quinnj) should work cleanly on 1.0 (I am testing it today and all works). If you find any problems please submit an issue.

---

<div class="post-metadata">

**Author:** ![tobias.knopp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tobias.knopp/32/7551_2.png) [@tobias.knopp](https://discourse.julialang.org/u/tobias.knopp)\
**Post date:** [August 8, 2018, 1:30pm UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/19 "2018-08-08T13:30:00Z")

</div>

> [@bernhard](#):
>
> I think there are a numer of packages (Distributions, DataFrames, PyCall, simply the popular ones on pulse) which should work flawlessly before releasing 1.0.

is there an overview which packages work and which not?

I would hope that all `Images` packages are working. And of course `Gtk` where some help might be needed.

---

<div class="post-metadata">

**Author:** ![piever](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/piever/32/1815_2.png) [@piever](https://discourse.julialang.org/u/piever)\
**Post date:** [August 8, 2018, 1:34pm UTC](https://discourse.julialang.org/t/julia-v1-0-rc1-is-now-available/13008/20 "2018-08-08T13:34:59Z")

</div>

Parts of the web stack are also transitioning from HttpServer to HTTP during this update, so things are not yet fully functional (at least for Blink, WebIO and to a lesser extent Mux).

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