# 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:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)\
**Post date:** [February 27, 2022, 8:22pm UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/1 "2022-02-27T20:22:33Z")

</div>

The Julia developers are pleased to announce that Julia v1.8.0 is now in beta. You can download binaries for the first beta release, v1.8.0-beta1, at [https://julialang.org/downloads](https://julialang.org/downloads) in the “upcoming release” section. Check out the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.8.0-beta1/NEWS.md) to see what will be new in 1.8.0. Binaries are available for the following platforms, listed here by [support tier](https://julialang.org/downloads/#supported_platforms):

- Tier 1:
  - macOS x86\_64 (Intel or Rosetta)
  - Window x86\_64
  - Linux x86\_64 (glibc)
  - Linux i686 (glibc)

- Tier 2:
  - FreeBSD x86\_64
  - Windows i686
  - Linux AArch64 (glibc)

- Tier 3:
  - macOS AArch64 (M-series)
  - Linux x86\_64 (musl)

As a beta version, this should **not** be considered production-ready. Rather, it’s intended to give users, especially package developers, a chance to try out their code with 1.8.0 prior to a full release. Note that `1.8` on [Travis](https://docs.travis-ci.com/user/languages/julia/), [AppVeyor](https://github.com/JuliaCI/Appveyor.jl), and [Cirrus](https://github.com/ararslan/CirrusCI.jl) now refers to 1.8.0-beta1. On [GitHub Actions](https://github.com/julia-actions/setup-julia), use `~1.8.0-0`.

Let us know in the [issue tracker](https://github.com/JuliaLang/julia/issues) if you run into any issues. Please note that any bugs you may encounter should be posted there rather than being discussed in this thread to ensure visibility to the developers.

---

<div class="post-metadata">

**Author:** ![cortner](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cortner/32/204_2.png) [@cortner](https://discourse.julialang.org/u/cortner)\
**Post date:** [February 27, 2022, 9:47pm UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/2 "2022-02-27T21:47:34Z")

</div>

Curious why M series is still Tier 3 ? Any prospect of full native support in the near future?

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [February 27, 2022, 9:53pm UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/3 "2022-02-27T21:53:32Z")

</div>

Quoting from [Download Julia](https://julialang.org/downloads/#support_tiers_for_the_latest_stable_release_of_julia)

> Tier 1: Julia is guaranteed to build from source and pass all tests on these platforms when built with the default options. Official binaries are always available and CI is run on every commit to ensure support is actively maintained.  
> …  
> Tier 3: Julia may or may not build. If it does, it is unlikely to pass tests. Binaries may be available in some cases. When they are, they should be considered experimental. Ongoing support is dependent on community efforts.

In particular, at the moment there is no CI at all for this platform, so it can’t qualify for Tier 1.

---

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [February 28, 2022, 12:37am UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/4 "2022-02-28T00:37:11Z")

</div>

> `Module(:name, false, false)` can be used to create a `module` that contains no names (it does not import `Base` or `Core` and does not contain a reference to itself) ([#40110, #42154]).

is missing hyperlink

---

<div class="post-metadata">

**Author:** ![cortner](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cortner/32/204_2.png) [@cortner](https://discourse.julialang.org/u/cortner)\
**Post date:** [February 28, 2022, 2:05am UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/5 "2022-02-28T02:05:25Z")

</div>

I know - hence my question.

---

<div class="post-metadata">

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

</div>

They need to have the hardware to use it for CI, perhaps that is the issue.

---

<div class="post-metadata">

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

</div>

How much would the hardware for CI cost? Is GoFundMe a possibility?

---

<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 …

---

<div class="post-metadata">

**Author:** ![tbeason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tbeason/32/15898_2.png) [@tbeason](https://discourse.julialang.org/u/tbeason)\
**Post date:** [February 28, 2022, 1:55pm UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/9 "2022-02-28T13:55:59Z")

</div>

I was only speculating. It seems the linked thread has all of the necessary details.

---

<div class="post-metadata">

**Author:** ![jlperla](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jlperla/32/34332_2.png) [@jlperla](https://discourse.julialang.org/u/jlperla)\
**Post date:** [March 1, 2022, 12:21am UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/10 "2022-03-01T00:21:07Z")

</div>

Is this supported on `juliaup`? I did `juliaup add beta` but it seems to point at the `1.7` release?

---

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [March 1, 2022, 5:30am UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/11 "2022-03-01T05:30:25Z")

</div>

Do `juliaup self update` first. It should work after this

---

<div class="post-metadata">

**Author:** ![airpmb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/airpmb/32/7826_2.png) [@airpmb](https://discourse.julialang.org/u/airpmb)\
**Post date:** [March 7, 2022, 5:50pm UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/12 "2022-03-07T17:50:56Z")

</div>

Pretty minor point but, it would be nice to have links to release notes on the [Download Julia](https://julialang.org/downloads/) page.

Looking forward to checking out the new features!

---

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [March 10, 2022, 6:52am UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/13 "2022-03-10T06:52:14Z")

</div>

The link “tiers of support” on [the download page](https://julialang.org/downloads/#currently_supported_platforms) that, I guess, would have lead to a page explaining the meaning of the various tiers, is broken…

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [March 10, 2022, 7:05am UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/14 "2022-03-10T07:05:48Z")

</div>

Well, the explanation is on the same page a in the next section.

---

<div class="post-metadata">

**Author:** ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Post date:** [March 10, 2022, 8:06am UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/15 "2022-03-10T08:06:38Z")

</div>

Can you open an issue on [https://github.com/JuliaLang/www.julialang.org](https://github.com/JuliaLang/www.julialang.org) to report the broken link?

---

<div class="post-metadata">

**Author:** ![astrobc1](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/astrobc1/32/45632_2.png) [@astrobc1](https://discourse.julialang.org/u/astrobc1)\
**Post date:** [March 15, 2022, 3:37pm UTC](https://discourse.julialang.org/t/julia-v1-8-0-beta1-is-now-available/77166/16 "2022-03-15T15:37:48Z")

</div>

Can beta releases start making their way to the official Julia docs? There’s always a gap between the current stable version and the dev versions - so right now there’s 1.7.2 then 1.9-dev. I know there’s a news.md file on GitHub with some info but having this in a central location seems best.