ziglang/ziglang.org
14
29
Fork
You've already forked ziglang.org
31

Remove (most) 32-bit x86 builds from the download page #619

Open
opened 2026年05月21日 08:21:03 +02:00 by alexrp · 2 comments

After some discussion in the team, there seems to be agreement on the following:

  • x86-linux will be removed once Debian Bookworm long-term support ends on June 30, 2028.
  • x86-windows will be removed once Windows 10 Enterprise LTSC 2021 support ends on January 12, 2027.
  • x86-netbsd will stay for now since NetBSD's whole thing is running on toasters.

To be clear, this will not affect Zig's ability to compile for and run on those targets, nor will it affect zig-bootstrap; this is just about which binaries we provide on the download page.

After some discussion in the team, there seems to be agreement on the following: * `x86-linux` will be removed once Debian Bookworm long-term support ends on June 30, 2028. * `x86-windows` will be removed once Windows 10 Enterprise LTSC 2021 support ends on January 12, 2027. * `x86-netbsd` will stay for now since NetBSD's whole thing is running on toasters. To be clear, this will not affect Zig's ability to compile for and run on those targets, nor will it affect [zig-bootstrap](https://codeberg.org/ziglang/zig-bootstrap); this is just about which binaries we provide on the download page.

The title of this issue gives a bit of the impression that items that are currently on the download page, are going to be removed and may no longer be downloadable.
That might be necessary to save some disc space ( 454Mb total 9 times x86-linux, and 746Mb total also 9 times x86-windows), or to keep the download page length manageable.

If possible I would suggest to only drop x86 for new versions that are being built (release versions and dev versions), if that is already the plan the title of this issue could be updated to "no longer offer new 32-bit x86 builds on the download page" to reflect that. If necessary for brevity we could cull the number of versions listed on the download page, but keep the downloadable files and keep them listed JSON version of that page), or have a shorter version (dev + last two releases) and complete version (everything, same as JSON).

Whatever the fate of the downloads/page, the same should probably apply to i386-linux ( 380Mb total in nine downloads) and i386-windows (409Mb in seven downloads).

The title of this issue gives a bit of the impression that items that are currently on the download page, are going to be removed and may no longer be downloadable. That might be necessary to save some disc space ( 454Mb total 9 times x86-linux, and 746Mb total also 9 times x86-windows), or to keep the download page length manageable. If possible I would suggest to only drop `x86` for new versions that are being built (release versions and dev versions), if that is already the plan the title of this issue could be updated to "no longer offer new 32-bit x86 builds on the download page" to reflect that. If necessary for brevity we could cull the number of versions listed on the download page, but keep the downloadable files and keep them listed JSON version of that page), or have a shorter version (dev + last two releases) and complete version (everything, same as JSON). Whatever the fate of the downloads/page, the same should probably apply to `i386-linux` ( 380Mb total in nine downloads) and `i386-windows` (409Mb in seven downloads).
Author
Owner
Copy link

@anthon wrote in #619 (comment):

If possible I would suggest to only drop x86 for new versions that are being built

This is the intent; we do not remove tagged release builds.

Dev builds are subject to deletion at any time, however.

@anthon wrote in https://codeberg.org/ziglang/ziglang.org/issues/619#issuecomment-16088102: > If possible I would suggest to only drop `x86` for new versions that are being built This is the intent; we do not remove tagged release builds. Dev builds are subject to deletion at any time, however.
Sign in to join this conversation.
No Branch/Tag specified
main
release-0.16.0
apraga/french
homersimpsons/fix/mobile-responsiveness
MarkLagodych/patch-1
Zirunis/patch-1
zmitchell/zmitchell/build-graph-docs
generalmimon/fix-unit-testing-examples
generalmimon/fix-code-snippet-in-0.15.1-relnotes
TheConnorJohnson/main
meeting-minutes
enkvadrat/update-curl-example
No results found.
Labels
Clear labels
bounty
https://ziglang.org/news/announcing-donor-bounties
bug
Observed behavior contradicts documented or intended behavior.
contributor-friendly
This issue is limited in scope and/or knowledge of project internals.
downstream
An issue with a third-party project that uses this project.
enhancement
Solving this issue will likely involve adding new logic or components to the codebase.
infra
An issue related to project infrastructure, e.g. continuous integration.
optimization
A task to improve performance and/or resource usage.
question
No questions on the issue tracker; use a community space instead.
regression
Something that used to work in a previous version stopped working
upstream
An issue with a third-party project that this project uses.
use case
Describes a real use case that is difficult or impossible, but does not propose a solution.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ziglang/ziglang.org#619
Reference in a new issue
ziglang/ziglang.org
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?