# Julia 1.8, 1.9 (rapid release?)

**URL:** <https://discourse.julialang.org/t/julia-1-8-1-9-rapid-release/85949>\
**Category:** General Usage\
**Created:** [August 18, 2022, 8:05pm UTC](https://discourse.julialang.org/t/julia-1-8-1-9-rapid-release/85949 "2022-08-18T20:05:50Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [August 19, 2022, 6:11pm UTC](https://discourse.julialang.org/t/julia-1-8-1-9-rapid-release/85949/16 "2022-08-19T18:11:01Z")

</div>

> [@Palli](#):
>
> It felt like 1.8 was delayed (due date cancelled)

As I’ve said before:

> [@The future of Julia, 1.6, 1.7-rc1, 1.8, 1.9, 1.10 and 2.0 and LTS](https://discourse.julialang.org/t/the-future-of-julia-1-6-1-7-rc1-1-8-1-9-1-10-and-2-0-and-lts/68143/3):
>
> Don’t pay too much attention to GitHub milestones. They’re internal organizational tools, not external promises.

The blog post I linked above discussed how the time _after_ a feature freeze is _intentionally_ variable. v1.8 hit [feature freeze in February](https://github.com/JuliaLang/julia/commit/7b395153e80672f8cdb18f51dd653a85e28b2070). Everything after that was in the **stabilization** phase. This release just took a long time to stabilize.

We’ll do patch releases on v1.8 as needed until v1.9 is released.

---

_[View the full topic](https://discourse.julialang.org/t/julia-1-8-1-9-rapid-release/85949)._