# 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:** 1\
**Showing post:** 7

<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 22, 2019, 11:13am UTC](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742/7 "2019-08-22T11:13:16Z")

</div>

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?

---

_[View the full topic](https://discourse.julialang.org/t/julia-v1-2-0-has-been-released/27742)._