# The 0.17.0 release cycle will be short, they said **URL:** \ **Category:** News\ **Created:** [September 18, 2026, 2:24pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644 "2026-09-18T14:24:48Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![truly-not-taken](https://ziggit.dev/user_avatar/ziggit.dev/truly-not-taken/32/6205_2.png) [@truly-not-taken](https://ziggit.dev/u/truly-not-taken)\ **Post date:** [September 18, 2026, 2:24pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/1 "2026-09-18T14:24:49Z")
Remember Roadmap in 0.16 release notes? It is not short after all. @andrewrk says this in zulip: > wow. what a detour. the 0.17 milestone continues to bless me with deceptively complex issues [#std \> rubber ducking @ šŸ’¬](https://zsf.zulipchat.com/#narrow/channel/454371-std/topic/rubber.20ducking/near/624789857) I do not expect 0.17 to be released before the end of the month. edit: a reply with most likes: > [@The 0.17.0 release cycle will be short, they said](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/9): > > My mistake was giving into the temptation to land the build system branch because I didnā€™t want it to rot. Problem is that it had a bunch of follow-up issues that really needed to be done before the tag, not the least of which was working with @Techatrix from ZLS team to make sure ZLS can continue to function correctly in 0.17. Those are the main release blockers at the moment. On the other hand, the good news is that while the tag is delayed, progress on other features has not. For example, 0.ā€¦ ---
**Author:** ![Southporter](https://ziggit.dev/user_avatar/ziggit.dev/southporter/32/2500_2.png) [@Southporter](https://ziggit.dev/u/Southporter)\ **Post date:** [September 18, 2026, 2:28pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/2 "2026-09-18T14:28:46Z")
Iā€™ve been thinking the same thing. It was _supposed_ to be _just_ updating LLVM. Iā€™m fine with letting them cook. It will be ready when itā€™s ready. ---
**Author:** ![Salmon](https://ziggit.dev/user_avatar/ziggit.dev/salmon/32/10236_2.png) [@Salmon](https://ziggit.dev/u/Salmon)\ **Post date:** [September 18, 2026, 2:52pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/3 "2026-09-18T14:52:26Z")
Sorry for off-topic but I am really eager to know: > having a working debugger is so nice Is this sarcasm or is there a good way to enter debug mode in Zig? I have tried some of the LLDB solutions that people have suggested but I found it quite hard to get it right (not sure if it was my fault or itā€™s just buggy). ---
**Author:** ![biom4st3r](https://ziggit.dev/user_avatar/ziggit.dev/biom4st3r/32/4342_2.png) [@biom4st3r](https://ziggit.dev/u/biom4st3r)\ **Post date:** [September 18, 2026, 3:05pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/4 "2026-09-18T15:05:53Z")
Idk about lldb but Gdb has always been kind to me for zig ---
**Author:** ![ultiman3rd](https://ziggit.dev/user_avatar/ziggit.dev/ultiman3rd/32/8222_2.png) [@ultiman3rd](https://ziggit.dev/u/ultiman3rd)\ **Post date:** [September 18, 2026, 3:06pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/5 "2026-09-18T15:06:37Z")
I was waiting for 0.17 for the new LLVM version to move my C project from CMake to Zig build. I ended up just using an 0.17-dev version to get the new LLVM in Zig and thatā€™s worked great for me šŸ™‚ ---
**Author:** ![jeffective](https://ziggit.dev/user_avatar/ziggit.dev/jeffective/32/3116_2.png) [@jeffective](https://ziggit.dev/u/jeffective)\ **Post date:** [September 18, 2026, 3:38pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/6 "2026-09-18T15:38:05Z")
The law of inaccurate engineering estimates remains unblemished. Fie! ---
**Author:** ![truly-not-taken](https://ziggit.dev/user_avatar/ziggit.dev/truly-not-taken/32/6205_2.png) [@truly-not-taken](https://ziggit.dev/u/truly-not-taken)\ **Post date:** [September 18, 2026, 4:17pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/7 "2026-09-18T16:17:51Z")
> [@Salmon](#): > > is there a good way to enter debug mode in Zig? Yes, if you have access to 0.17, [I guess](https://codeberg.org/ziglang/zig/issues/35791). ---
**Author:** ![Rework7438](https://ziggit.dev/user_avatar/ziggit.dev/rework7438/32/8867_2.png) [@Rework7438](https://ziggit.dev/u/Rework7438)\ **Post date:** [September 20, 2026, 1:38pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/8 "2026-09-20T13:38:36Z")
I love NND on linux [GitHub - al13n321/nnd: A debugger for Linux Ā· GitHub](https://github.com/al13n321/nnd) I donā€™t do incredibly complex debugging but this one is nice ---
**Author:** ![andrewrk](https://ziggit.dev/user_avatar/ziggit.dev/andrewrk/32/7011_2.png) [@andrewrk](https://ziggit.dev/u/andrewrk)\ **Post date:** [September 20, 2026, 8:34pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/9 "2026-09-20T20:34:58Z")
My mistake was giving into the temptation to land the build system branch because I didnā€™t want it to rot. Problem is that it had a bunch of follow-up issues that really needed to be done before the tag, not the least of which was working with @Techatrix from ZLS team to make sure ZLS can continue to function correctly in 0.17. Those are the main release blockers at the moment. On the other hand, the good news is that while the tag is delayed, progress on other features has not. For example, 0.17 will greatly increase the robustness and practical usability of incremental compilation, in particular with respect to debug information and linker capability. Similarly, the way that ZLS and build system communicate now opens the doors to some nice future enhancements. With all that in mind, the fact that I didnā€™t successfully pull off a short release cycle means that there is still the need to do a short release cycle to catch up with LLVM. ---
**Author:** ![yinameah](https://ziggit.dev/user_avatar/ziggit.dev/yinameah/32/8453_2.png) [@yinameah](https://ziggit.dev/u/yinameah)\ **Post date:** [September 20, 2026, 9:48pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/10 "2026-09-20T21:48:56Z")
Iā€™m quite happy with this ā€œdelayā€. Things taste better when property awaited for. Looking forward to incr-compile all sorts of things šŸ˜. Quietly looking forward ---
**Author:** ![gwenzek](https://ziggit.dev/user_avatar/ziggit.dev/gwenzek/32/8137_2.png) [@gwenzek](https://ziggit.dev/u/gwenzek)\ **Post date:** [September 21, 2026, 9:41am UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/11 "2026-09-21T09:41:01Z")
Is 0.17 still targeting LLVM 22 (with the auto vectorizer bug), or are you gonna jump straight to LLVM 23 ? ---
**Author:** ![andrewrk](https://ziggit.dev/user_avatar/ziggit.dev/andrewrk/32/7011_2.png) [@andrewrk](https://ziggit.dev/u/andrewrk)\ **Post date:** [September 21, 2026, 4:55pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/12 "2026-09-21T16:55:31Z")
Itā€™s good to have a release for every version of LLVM because it means that for Linux distributions which only have 22 packaged, they will be able to package Zig 0.17.x as well. Of course, until [make the main zig executable no longer depend on LLVM, LLD, and Clang libraries Ā· Issue #16270 Ā· ziglang/zig Ā· GitHub](https://github.com/ziglang/zig/issues/16270) is completed. Then Zig will have an independent release cadence. ---
**Author:** ![marler8997](https://ziggit.dev/user_avatar/ziggit.dev/marler8997/32/77_2.png) [@marler8997](https://ziggit.dev/u/marler8997)\ **Post date:** [September 21, 2026, 5:08pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/13 "2026-09-21T17:08:28Z")
Iā€™ve been stuck on 0.15.2 due to [https://codeberg.org/ziglang/zig/issues/31865](https://codeberg.org/ziglang/zig/issues/31865) (causes any `zig build` command to fail on windows ARM). If 0.17 is gonna continue to be delayed, could we get a 0.16.1 release that fixes this so I can start upgrading everything? P.S. Itā€™s also starting to get awkward as 0.15.2 also fails on macos with Xcode 27ā€¦so if I stay on 0.15 I canā€™t run `zig build` on macos, if I upgrade to 0.16 I canā€™t run `zig build` on windows arm. ---
**Author:** ![eag](https://ziggit.dev/letter_avatar_proxy/v4/letter/e/ba8739/32.png) [@eag](https://ziggit.dev/u/eag)\ **Post date:** [October 1, 2026, 8:46pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/14 "2026-10-01T20:46:32Z")
This post was flagged by the community and is temporarily hidden. ---
**Author:** ![bcrist](https://ziggit.dev/user_avatar/ziggit.dev/bcrist/32/7935_2.png) [@bcrist](https://ziggit.dev/u/bcrist)\ **Post date:** [October 1, 2026, 9:40pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/15 "2026-10-01T21:40:50Z")
Welcome to Ziggit! While I can piece together what some of your sentences might mean, Iā€™m having trouble putting them together into any coherent thought related to Andrewā€™s message, or anything else in this thread, for that matter. What does come across is that your tone feels somewhat hostile. So I have two recommendations for you: 1. Please be polite and respectful, even if you are frustrated or if what you want to say is a complaint. Communicating with people on the internet for the first time is no different from interacting in-person with someone you donā€™t know. Keep in mind that just as you are free to think whatever you want, everyone else is free to disregard your thoughts, and using condescending or aggressive language will only encourage the latter. 2. If you do not feel fluent enough in English to compose your thoughts or verify that the output of a translation service is reasonable, feel free to just post in your native language and let others use the translation service of their choosing. ---
**Author:** ![Plebosaur](https://ziggit.dev/user_avatar/ziggit.dev/plebosaur/32/6857_2.png) [@Plebosaur](https://ziggit.dev/u/Plebosaur)\ **Post date:** [October 1, 2026, 10:38pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/16 "2026-10-01T22:38:57Z")
A few days ago the last issue with the 0.17 milestone was closed. So hopefully fingers crossed it will come soon. ---
**Author:** ![cicerovargas](https://ziggit.dev/user_avatar/ziggit.dev/cicerovargas/32/10250_2.png) [@cicerovargas](https://ziggit.dev/u/cicerovargas)\ **Post date:** [October 1, 2026, 10:53pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/17 "2026-10-01T22:53:38Z")
šŸ‘€ > **[Public view of Zig Software Foundation | Zulip team chat](https://zsf.zulipchat.com/#narrow/channel/454416-notifications/topic/codeberg/near/628504810)** > > Browse the publicly accessible channels in Zig Software Foundation without logging in. ---
**Author:** ![truly-not-taken](https://ziggit.dev/user_avatar/ziggit.dev/truly-not-taken/32/6205_2.png) [@truly-not-taken](https://ziggit.dev/u/truly-not-taken)\ **Post date:** [October 1, 2026, 11:26pm UTC](https://ziggit.dev/t/the-0-17-0-release-cycle-will-be-short-they-said/17644/18 "2026-10-01T23:26:22Z")
An hour ago @andrewrk said: > approximately 22 hours until download page updated and release notes go up [#ecosystem \> general chat @ šŸ’¬](https://zsf.zulipchat.com/#narrow/channel/454446-ecosystem/topic//near/628506262)