NixOS 24.05 — Release Schedule

Hi, we are [Weijia Wang](https://github.com/wegank) & [Jörg Thalheim](https://github.com/Mic92), the [release managers](https://nixos.github.io/release-wiki/Release-Managers.html) for NixOS 24.05 ("_Uakari_").

We're also happy to work with [Jacek Generowicz](https://github.com/jacg), who will be the [release editor](https://nixos.github.io/release-wiki/Release-Editors.html) for this NixOS release.

Below you can find the release calendar for the next two months running up to the planned release at the end of May 2024. If something feels unclear to you, don't hesitate to reach out, we are here to guide the process and make sure this will be a satisfying release for all of us.

Stay tuned for updates!

<table>
    <tr>
        <td></td>
        <td>Date</td>
        <td>Affects</td>
        <td>Events</td>
    </tr>
    <tr>
        <td>:heavy_check_mark:</td>
        <td>2024-04-11</td>
        <td>—</td>
        <td>Start <a href="https://github.com/NixOS/nixpkgs/issues/303286">discussion</a> about "Feature Freeze & Release Blockers" with ecosystem maintainers</td>
    </tr>
    <tr>
        <td>:heavy_check_mark:</td>
        <td>2024-04-17</td>
        <td>all branches</td>
        <td>Restrict breaking changes to <a href="https://nixos.github.io/release-wiki/Release-Critical-Packages.html">Release Critical Packages</a></td>
    </tr>
    <tr>
        <td>:heavy_check_mark:</td>
        <td>2024-05-01</td>
        <td>all branches</td>
        <td>Restrict all breaking changes with the exception of desktop environments</td>
    </tr>
    <tr>
        <td rowspan="2">:heavy_check_mark:</td>
        <td rowspan="2">2024-05-08</td>
        <td><tt>master</tt></td>
        <td>Wait for <tt>staging-next</tt> merge into <tt>master</tt>; begin first <tt>staging-next</tt> cycle</td>
    </tr>
    <tr>
        <td><tt>master</tt></td>
        <td>Begin Zero Hydra Failures campaign</td>
    </tr>
    <tr>
        <td rowspan="2">:heavy_check_mark:</td>
        <td rowspan="2">2024-05-15</td>
        <td><tt>master</tt></td>
        <td>Wait for first <tt>staging-next</tt> merge into <tt>master</tt>; begin second <tt>staging-next</tt> cycle</td>
    </tr>
    <tr>
        <td><tt>staging</tt></td>
        <td>Unrestrict all breaking changes; new changes will not be present in the release</td>
    </tr>
    <tr>
        <td rowspan="8">:heavy_check_mark:</td>
        <td rowspan="8">2024-05-22</td>
        <td><tt>master</tt></td>
        <td>Wait for second <tt>staging-next</tt> merge into <tt>master</tt></td>
    </tr>
    <tr>
        <td><tt>staging-next</tt></td>
        <td>Unrestrict all breaking changes; new changes will not be present in the release</td>
    </tr>
    <tr>
        <td><tt>master</tt></td>
        <td>Mark failing packages as broken</td>
    </tr>
    <tr>
        <td><tt>master</tt>, <tt>release-24.05</tt></td>
        <td>Branch-off</td>
    </tr>
    <tr>
        <td><tt>master</tt>, <tt>release-24.05</tt></td>
        <td>Tag <tt>24.05-beta</tt> on <tt>release-24.05</tt><br /> and <tt>24.05-unstable</tt> on <tt>master</tt></td>
    </tr>
    <tr>
        <td><tt>master</tt>, <tt>release-24.05</tt></td>
        <td>Create release channels</td>
    </tr>
    <tr>
        <td><tt>master</tt>, <tt>release-24.05</tt></td>
        <td>ZHF fixes go into <tt>master</tt> and need to be backported to <tt>release-24.05</tt></td>
    </tr>
    <tr>
        <td><tt>release-24.05</tt></td>
        <td>Prepare for release, finish remaining issues</td>
    </tr>
    <tr>
        <td>:heavy_check_mark:</td>
        <td>2024-05-31</td>
        <td><tt>release-24.05</tt></td>
        <td>Release! Also, ZHF ends</td>
    </tr>
    <tr>
        <td></td>
        <td>2024-06-09</td>
        <td>—</td>
        <td>Release Retrospective, everyone is invited to give feedback!</td>
    </tr>
</table>

---

## Definitions

- Backport
  - Cherry-picking a change from `master` into `release-24.05`
  - Use the backport action by applying the `backport: release-24.05` tag
- Breaking change
  - A change that is likely to break downstream consumers
- Ecosystem maintainers
  - Maintainer teams that have enabled `enableFeatureFreezePing` in [`maintainers/team-list.nix`](https://github.com/NixOS/nixpkgs/blob/master/maintainers/team-list.nix)
- [Release Critical Packages](https://nixos.github.io/release-wiki/Release-Critical-Packages.html)
  - List of packages that usually cause widespread breakages
- Restriction
  - Changes of the mentioned kind cannot be merged while the restriction is active
- ZHF
  - Zero Hydra Failures
  - Period in which contributors focus on stabilizing packages
  - Usually through PRs targeted at the `master` branch


	Date	Affects	Events
✔️	2024-04-11	—	Start discussion about "Feature Freeze & Release Blockers" with ecosystem maintainers
✔️	2024-04-17	all branches	Restrict breaking changes to Release Critical Packages
✔️	2024-05-01	all branches	Restrict all breaking changes with the exception of desktop environments
✔️	2024-05-08	`master`	Wait for `staging-next` merge into `master`; begin first `staging-next` cycle
✔️	2024-05-08	`master`	Begin Zero Hydra Failures campaign
✔️	2024-05-15	`master`	Wait for first `staging-next` merge into `master`; begin second `staging-next` cycle
✔️	2024-05-15	`staging`	Unrestrict all breaking changes; new changes will not be present in the release
✔️	2024-05-22	`master`	Wait for second `staging-next` merge into `master`
		`staging-next`	Unrestrict all breaking changes; new changes will not be present in the release
		`master`	Mark failing packages as broken
		`master`, `release-24.05`	Branch-off
		`master`, `release-24.05`	Tag `24.05-beta` on `release-24.05` and `24.05-unstable` on `master`
		`master`, `release-24.05`	Create release channels
		`master`, `release-24.05`	ZHF fixes go into `master` and need to be backported to `release-24.05`
		`release-24.05`	Prepare for release, finish remaining issues
✔️	2024-05-31	`release-24.05`	Release! Also, ZHF ends
	2024-06-09	—	Release Retrospective, everyone is invited to give feedback!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

NixOS 24.05 — Release Schedule #303285

Definitions

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Uh oh!

NixOS 24.05 — Release Schedule #303285

Description

Definitions

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions