# 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:** 35

<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 24, 2019, 8:44am UTC](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623/35 "2019-01-24T08:44:36Z")

</div>

Just a bit of reflection on developments after 1.0: 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. I may have a biased view, but for interactive work (data analysis, model estimation, plotting) I think it is not unreasonable to just keep up with the latest minor release (perhaps after a tolerance period of a few weeks, for the extra-cautious). In the unlikely case that things break, one can always go back to 1.(x-1) and backport.

---

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