# Julia version change \[how much change , programmer should fear\]

**URL:** <https://discourse.julialang.org/t/julia-version-change-how-much-change-programmer-should-fear/51775>\
**Category:** Community\
**Created:** [December 13, 2020, 8:54pm UTC](https://discourse.julialang.org/t/julia-version-change-how-much-change-programmer-should-fear/51775 "2020-12-13T20:54:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vedasulo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vedasulo/32/20324_2.png) [@vedasulo](https://discourse.julialang.org/u/vedasulo)\
**Post date:** [December 13, 2020, 8:54pm UTC](https://discourse.julialang.org/t/julia-version-change-how-much-change-programmer-should-fear/51775/1 "2020-12-13T20:54:28Z")

</div>

I am quite learning julia. But It seems it is developing.  
I became fear, If suddenly julia release **julia 3.0 version** what would happen to older version like (python 2 vs python 3) python2 nobody cares now.

and why Julia have those **LTS** or **short** version.  
Why julia didnt take one version and gradually develop it without those terms?

(Also please give me notification with \*\*julia new release with new functionalities and capabilities and depretiation warning \*\*

---

<div class="post-metadata">

**Author:** ![oxinabox](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oxinabox/32/206603_2.png) [@oxinabox](https://discourse.julialang.org/u/oxinabox)\
**Post date:** [December 13, 2020, 9:12pm UTC](https://discourse.julialang.org/t/julia-version-change-how-much-change-programmer-should-fear/51775/2 "2020-12-13T21:12:06Z")

</div>

- Julia has been stable since the 1.0 release in 2018
- Julia is not planning on releasing 2.0 any time soon.
- When julia does do a 2.0, it will be far less painful than python 2.0 to 3.0, because everyone saw what a trash fire that was, and knows not to repeat it.
  - If you think you are worried about it / aware of it, just think how much more the core developers are.
  - I expect that Julia 2.0 will probably just be able to load julia 1.0 compatible packages in some form of Compat mode
  - I also expect some really good tools for migrating, like we had FemtoCleaner that moved things from 0.6 to 1.0, and made PRs to everyone’s repos.

- Nothing is breaks between minor releases, unless you access the internals (e.g. my package [Tricks.jl](https://github.com/oxinabox/Tricks.jl) has never broken yet, but it might). Julia tests all packages on all releases and makes sure nothing breaks (unless you are depending on internals)
- At any point in time 3 versions of julia are supported for getting bug-fixes if you open up a issue on github. These terms help clarify which versions you are able to get support for.
  - dev (i.e. nightly), where the fix will be made
  - stable: the current release (will get any bug fix included in its next patch release. Most stable releases have has 1-2 patch releases)
  - LTS: the long term support release. (generally will need to specifically mention you want it backported)

- The Stable version of julia is the one almos everyone should be using
- The Long Term Support release is for those that are are extremely risk adverse (e.g. some production enviroments) then it gets bug-fixes but not new features. That means it is less likely to have bugs inadventently added.

---

<div class="post-metadata">

**Author:** ![simeonschaub](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/simeonschaub/32/216566_2.png) [@simeonschaub](https://discourse.julialang.org/u/simeonschaub)\
**Post date:** [December 13, 2020, 10:15pm UTC](https://discourse.julialang.org/t/julia-version-change-how-much-change-programmer-should-fear/51775/3 "2020-12-13T22:15:08Z")

</div>

For even more details on Julia’s release process, also see this blog post:

> **[Julia’s Release Process](https://julialang.org/blog/2019/08/release-process/)**
>
> Julia’s Release Process | People involved in the day-to-day development of a project tend to become so familiar with its rhythm and process that they internalize it and it feels like everyone must just \_know\_ how each stage unfolds. Of course, from...

---

<div class="post-metadata">

**Author:** ![vedasulo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vedasulo/32/20324_2.png) [@vedasulo](https://discourse.julialang.org/u/vedasulo)\
**Post date:** [December 14, 2020, 3:46am UTC](https://discourse.julialang.org/t/julia-version-change-how-much-change-programmer-should-fear/51775/4 "2020-12-14T03:46:00Z")

</div>

Thank you @oxinabox , @simeonschaub .  
I thing i have nothing to worry like api changes. 🙂 all are stable

---

<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:** [December 14, 2020, 10:40am UTC](https://discourse.julialang.org/t/julia-version-change-how-much-change-programmer-should-fear/51775/5 "2020-12-14T10:40:40Z")

</div>

> [@oxinabox](#):
>
> When julia does do a 2.0, it will be far less painful than python 2.0 to 3.0

This is the key point — _if_ anything breaks, it will be in exchange for something that is really worth it. See also

> [@PSA: Julia is not at that stage of development anymore](https://discourse.julialang.org/t/psa-julia-is-not-at-that-stage-of-development-anymore/44872):
>
> You heard about this brand new exciting programming language called Julia and have some suggestions for how it should work. Wonderful! We’re happy to have you here and help you learn the language and listen to your ideas! However, please be aware that “new” is a relative term. Yes, Julia is newer than, say, C, which was first created in 1972 and standardized in 1989. It is not, however, new in the sense that it is still being freely designed and changed in arbitrary ways. Julia development start…