# 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\
**Page:** 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 25, 2019, 7:27am UTC](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623/41 "2019-01-25T07:27:06Z")

</div>

You are right, the only concern is bugfixes. Small projects (\approx 1 person) may not have the reources to backport everything, so for those encountering bugs the advice is usually upgrading. Which is fine, but if the new package version also requires a higher version of Julia, it can set up a cascade of upgrades.

Still, with version control all such experiments are reversible, so it is not that painful.

[Previous page](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623.md?page=2)