# Julia v1.2.0 has been released
**URL:** https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742
**Category:** Announcements
**Tags:** release
**Created:** [August 20, 2019, 6:39am UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742 "2019-08-20T06:39:52Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@ararslan](https://discourse.julialang.org/u/ararslan)
#### Post date: [August 20, 2019, 6:39am UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742/1 "2019-08-20T06:39:53Z")
The Julia developers are pleased to announce the release of Julia v1.2.0, the second minor release in the 1.x series. Binaries are available for Linux, Windows, macOS, and FreeBSD at [Download Julia](https://julialang.org/downloads).
As a minor release, v1.2.0 contains no breaking changes, only new features, performance improvements, and marginal, undisruptive changes in behavior. The best reference for the changes in 1.2 is the [NEWS file](https://github.com/JuliaLang/julia/tree/v1.2.0/NEWS.md) for 1.2.0.
Note that 1.2, like 1.1, does not have long term support. As of this release, 1.1 has been effectively superseded by 1.2, which means there will not likely be any further 1.1.x releases. Our good friend 1.0 is still currently the only long-term support version.
We encourage everyone to give it a try. Packages can test with 1.2.0 on CI by specifying `1.2` on Travis, AppVeyor (with [Appveyor.jl](https://github.com/JuliaCI/Appveyor.jl)), and Cirrus (using [CirrusCI.jl](https://github.com/ararslan/CirrusCI.jl)). As always, let us know in the [issue tracker](https://github.com/JuliaLang/julia/issues) if you run into any issues.
Happy coding!
---
### Author:  [@amrods](https://discourse.julialang.org/u/amrods)
#### Post date: [August 21, 2019, 6:12am UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742/2 "2019-08-21T06:12:40Z")
The link for the pdf manual for 1.2 at the top of [Julia Documentation · The Julia Language](https://docs.julialang.org/en/v1/) is not working. It gives a 404 error.
---
### Author:  [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [August 21, 2019, 9:07am UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742/3 "2019-08-21T09:07:26Z")
Fixed now.
---
### Author:  [@adriano.vilela](https://discourse.julialang.org/u/adriano.vilela)
#### Post date: [August 21, 2019, 12:34pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742/4 "2019-08-21T12:34:40Z")
In the pdf manual, each of the sections under “Julia v1.2 Release Notes” shows up as a separate chapter. Chapter 3 (Language changes), for example, is one line long. Not really a problem, but I think it would make more sense if the Release Notes were all contained in a single chapter.
---
### Author:  [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [August 21, 2019, 12:40pm UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742/5 "2019-08-21T12:40:02Z")
Sure, the PDF output could really use an overhaul. Feel free to contribute: [https://github.com/JuliaDocs/Documenter.jl](https://github.com/JuliaDocs/Documenter.jl) !
---
### Author:  [@StevenSiew](https://discourse.julialang.org/u/StevenSiew)
#### Post date: [August 22, 2019, 10:56am UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742/6 "2019-08-22T10:56:56Z")
When I upgraded from 1.0 to 1.1, someone gave me these instructions.
Are these instructions still valid for the upgrade of 1.1 to 1.2
```julia
Note that if you want to keep the same packages as in 1.0 you
can copy (or rename if you are no longer using julia 1.0)
the .julia/environments/v1.0 folder to .julia/environments/v1.1
$ cd ~/.julia
$ cd environments/
$ ls
v1.0
$ cp -rp v1.0 v1.1
$ ls -l
total 0
drwxr-xr-x 4 ssiew staff 136 18 Aug 2018 v1.0
drwxr-xr-x 4 ssiew staff 136 18 Aug 2018 v1.1
```
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [August 22, 2019, 11:13am UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742/7 "2019-08-22T11:13:16Z")
Pretty much yes, but of course you would have to modify
```julia
cp -rp v1.1 v1.2
```
if you are upgrading from 1.1.
symlinking everything to a common directory is also an alternative:
> [@Share package enviroments between 1.0 and master](https://discourse.julialang.org/t/share-package-enviroments-between-1-0-and-master/15988):
>
> Since I use both master and 1.0, I was wondering if I could somehow maintain a consistent environment of packages (ie the global Project.toml and Manifest.toml in ~/.julia/environments/VERSION) between the two, to make it easier to switch back and forth. Just checking, could this have any unintended downsides I am not seeing? Regarding the implementation, can I just symlink ~/.julia/environments/v1.1 etc to ~/.julia/environments/v1.1, or is there a more canonical way of doing this?