# Moving from v0.6 to v1.0 has been so annoying

**URL:** <https://discourse.julialang.org/t/moving-from-v0-6-to-v1-0-has-been-so-annoying/15740>\
**Category:** General Usage\
**Created:** [October 1, 2018, 3:39pm UTC](https://discourse.julialang.org/t/moving-from-v0-6-to-v1-0-has-been-so-annoying/15740 "2018-10-01T15:39:25Z")\
**Posts on this page:** 1\
**Showing post:** 32

<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:** [October 4, 2018, 9:25am UTC](https://discourse.julialang.org/t/moving-from-v0-6-to-v1-0-has-been-so-annoying/15740/32 "2018-10-04T09:25:10Z")

</div>

> [@Sukera](#):
>
> It seems that people don’t really want to read release notes if they can avoid it and just want to use the latest version - in which case they hopefully are aware that a major version jump is going to be breaking and are not surprised that it actually is.

While you are correct about this, in retrospect I think it is recognized that the purpose of 0.7 was not communicated widely enough. This was fixed ex post:

> [@PSA: use Julia 0.7 if you are upgrading](https://discourse.julialang.org/t/psa-use-julia-0-7-if-you-are-upgrading/13321):
>
> A lot of people are posting issues where their old code doesn’t work anymore on 1.0 because some function has been renamed or removed. The 0.7 release exists exactly for this reason: your old code will work on 0.7 and give you a specific warning about how to fix your code. If you have any old code, you should use 0.7 to get these warnings before switching to 1.0; even if you just have work habits that may need changing, you should probably use 0.7 for a while. If someone posts an issue like thi…

and I think it is reasonable to expect this will be done differently next time.

---

_[View the full topic](https://discourse.julialang.org/t/moving-from-v0-6-to-v1-0-has-been-so-annoying/15740)._