# Proposed release process and schedule

**URL:** <https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623>\
**Category:** Internals & Design\
**Tags:** proposal, releases\
**Created:** [September 28, 2018, 3:43pm UTC](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623 "2018-09-28T15:43:12Z")\
**Posts on this page:** 1\
**Showing post:** 36

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [January 24, 2019, 9:36am UTC](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623/36 "2019-01-24T09:36:20Z")

</div>

> [@Tamas\_Papp](#):
>
> since 1.1 contains so many nice new features _and_ bugfixes, I may just find it much easier to require 1.1 in my packages when they get a rewrite, simply to economize on developer effort.
> 
> I am still pondering over this, since it would mean that the “(very) low risk tolerance” users stuck on 1.0 for some reason either won’t get upgrades.

see also the discussion here on this topic

> [@Julia v1.1.0-rc1, the first 1.1 release candidate, is now available](https://discourse.julialang.org/t/julia-v1-1-0-rc1-the-first-1-1-release-candidate-is-now-available/19172/14):
>
> That makes sense, but my question was subtly more general than your answer satisfies. I’m also asking about the more general case when v1.x is released, let’s say v1.2, then it is recommended to continue testing for compatibility with v1.0 and v1.2, since v1.0 is long term. However, because v1.1 is a short term release, is it recommended to drop it from testing and only continue with v1.0 and v1.2 compatibility? Otherwise, the tests would keep getting longer and longer with each version. It do…

---

_[View the full topic](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623)._