# Julia v1.8.0-beta1 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166>\
**Category:** Announcements\
**Tags:** release\
**Created:** [February 27, 2022, 8:22pm UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166 "2022-02-27T20:22:33Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![ImreSamu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/imresamu/32/20677_2.png) [@ImreSamu](https://discourse.julialang.org/u/ImreSamu)\
**Post date:** [February 28, 2022, 12:35pm UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/8 "2022-02-28T12:35:42Z")

</div>

> [@tbeason](#):
>
> They need to have the hardware to use it for CI, perhaps that is the issue.

based on the “old thread” … it is not a hardware problem.  
_“M1 boxes may already be in the availability of the developers,”_

> [@Is there anything users can do to help move Apple Silicon support from Tier 3 to Tier 1?](https://discourse.julialang.org/t/is-there-anything-users-can-do-to-help-move-apple-silicon-support-from-tier-3-to-tier-1/72739/9):
>
> I don’t think that’s really useful before [https://github.com/JuliaLang/julia/issues/41440](https://github.com/JuliaLang/julia/issues/41440) is resolved. That’s the main stumbling block at the moment. All tests jobs are going to segfault because of that, it isn’t incredibily useful to run jobs that systematically crash for a well known issue. The problem is that that’s not trivial to address. Additionally, most (but not all?) Julia CI runs on on-premise hardware, I’m not sure renting overpriced cloud machines is the best option money-wise. M1 …

---

_[View the full topic](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166)._