List view
Resolve these issues before releasing 0.15.0. Criteria: * Regressions from the previous release. * Miscompilations. * Unblocks an active third party project using Zig. * Breaking changes that are better done earlier to minimize impact. * Subjective opinions of the Zig Core Team.
Due by July 30, 2025•2/56 issues closedThe Zig Core Team has no plans to tackle these issues. Community efforts are welcome. What makes something "unplanned"? * Dubious problem statement * Unverified bug * Relates to an esoteric target or use case * Unclear that a satisfactory resolution is achievable * Does not block any release
No due date•26/204 issues closedIntended to be worked on next. The Zig Core Team solves as many of these issues as possible for the upcoming release, however these issues do not block the release.
No due date•155/1605 issues closedPlanned but not pressing. Likely to remain unsolved in the next release.
No due date•14/1051 issues closedLowest possible priority while still being planned.
No due date•0/77 issues closedLowest possible priority while still blocking the release of 1.0.
No due date•0/77 issues closed