The builds and change notes are not yet up, so still fingers crossed that there aren’t any issues that delay it (or requires an immediate patch release cough 0.15 cough)
Shipping to production on a friday. Yikes.
I’ve read in another thread it will take around 22 hours for the binaries to be in the website.
So, while I wait patiently, I’ve been wondering : why does it takes such a lengthy-ish time?
Somehow I never wondered before, but I know it’s the same for the master builds.
Anybody familiar with the release process internal that would want to enlighten me?
We build LLVM and Zig for 27 platforms for tarballs.
So it’s really just 20 hours of compilation ? Gosh, impressive.
So you don’t build every commit in master, right? How do you decide when to update the tarball for the dev version? Is it a manual process?
Anyways, thanks for the amazing job and finger crossed I guess 
The tarballs workflow runs on a cron schedule: https://codeberg.org/ziglang/ziglang.org/src/commit/69ff592d72305c6f5e6ed59cb677aef0711eb601/.forgejo/workflows/build-tarballs.yml#L5
Once run, it picks the most recent green build from ziglang/zig and builds tarballs for that; we don’t build tarballs for every push.
Advanced users can override the cache poisoning behavior with a new CLI option:
--cache-poison[=mode] Override configuration caching behavior pure (default) Avoid false positive cache hits poisoned Don't cache the configuration disallowed Panics when cache would be poisoned ignored A little poison never hurt anybody
This is hilarious 