# Julia v1.1.0 has been released

**URL:** <https://discourse.julialang.org/t/julia-v1-1-0-has-been-released/19911>\
**Category:** Announcements\
**Tags:** release\
**Created:** [January 22, 2019, 4:04am UTC](https://discourse.julialang.org/t/julia-v1-1-0-has-been-released/19911 "2019-01-22T04:04:13Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [January 22, 2019, 8:09am UTC](https://discourse.julialang.org/t/julia-v1-1-0-has-been-released/19911/3 "2019-01-22T08:09:47Z")

</div>

> [@StevenSiew](#):
>
> If not, then there is no reason not to upgrade to Julia v1.1.0

In general, there is no reason not to upgrade to v1.1.0, except in the very unlikely case that a “minor change” breaks something for you, possibly in an unregistered package. See

> [@Proposed release process and schedule](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623):
>
> Now that we’ve released Julia 1.0 and are [close to 1.0.1](https://discourse.julialang.org/t/julia-1-0-1-testing-period/15534) and have added some [new features](https://github.com/JuliaLang/julia/pulls?utf8=%E2%9C%93&q=is%3Apr+label%3Aenhancement) and [minor changes](https://github.com/JuliaLang/julia/pulls?utf8=%E2%9C%93&q=is%3Apr+label%3A%22minor+change%22) to the 1.1 development branch (i.e. master), it seems like time to talk about the future of the Julia release process. After various discussions in person, on Slack, and on this week’s triage call, it seems like there’s fairly solid consensus behind the following plan. Patch releases Patch releases increment the last digit of Julia’s version number, e.g. going from 1.0.0 to 1.0.1 curre…

---

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