| 24 Apr 2025 |
 Arian | * I want to drop the amazonImage job from the release blockers in hydra as I'm about to move the build to github actions . Do I need to do that before today? Or is that fine to do whilst we're in the release process? | 10:13:12 |
 Mic92 | Sounds fine to me? | 10:51:29 |
|  Stallman Wang joined the room. | 10:51:36 |
 emily | does the actual job get removed at some point? | 10:56:28 |
| emily | Hydra will build it regardless of whether it's a blocker so is the intent to drop it for 25.05 or just let it break? | 10:56:53 |
| Mic92 | Would be good if we could actually drop it. | 11:24:54 |
 vcunat | Yes, big images are relatively expensive for the infra. | 11:26:13 |
| Arian | Yeh I will remove the job | 11:28:29 |
| Arian | I am replacing it with an amazonConfig job that builds the NixOS config inside the image; but not the image itself | 11:28:46 |
| emily | do you expect anyone outside the project is consuming the image job? | 11:29:35 |
| emily | Nix 2.28 regression: https://github.com/NixOS/nix/issues/13050, cc leona, I assume a 2.28.x release is imminent | 12:43:05 |
| emily | ah, https://github.com/NixOS/nixpkgs/pull/401428 has a patch. | 12:43:50 |
| 25 Apr 2025 |
 Tristan Ross | leona: https://github.com/NixOS/nixpkgs/pull/397932 is technically a breaking change but I'd like to get it into 25.05 since it means next system update I do, I could try Steam on Apple Silicon without doing it so hacky. Reason why I think it's fine, it's just a rename and it bumps to a newer version that can actually work. | 02:25:53 |
 leona | In reply to @rosscomputerguy:matrix.org
leona: https://github.com/NixOS/nixpkgs/pull/397932 is technically a breaking change but I'd like to get it into 25.05 since it means next system update I do, I could try Steam on Apple Silicon without doing it so hacky. Reason why I think it's fine, it's just a rename and it bumps to a newer version that can actually work. Okay for me | 08:28:01 |
| 29 Apr 2025 |
| Arian | For some reason the unstable channel was published as beta instead of pre for a while https://releases.nixos.org/?prefix=nixos/unstable/
Apprently from . Was this some bug/mishap in the release process?
from 2024-11-20 until 2025-3-23
It’s breaking some scripts I have locally :D
My understanding is that the unstable channel should always be pre-release. Only the beta branch for a stable release should be published as beta. Any idea what happened here?
| 09:43:15 |
| leona | This was a manual mistake in the release process. There is some conversation about this a month ago in this channel | 09:44:03 |
| leona | i.e. the change to beta was committed to master and release-24.11 instead of only to release-24.11 | 09:45:03 |
| Arian | Cool. makes sense | 09:46:07 |
|  @federicodschonborn:matrix.org changed their display name from This LEGO® Worm™ is licensed under the terms of the he/him or they/them pronouns, at your choice to This legally distinct plastic brick is licensed under the terms of the he/him or they/them pronouns, at your choice. | 14:41:28 |
| leona | Does anyone have an opinion on whether to start tomorrow with ZHF before the last breaking changes from staging-next are merged or wait for that until staging-next is merged? It feels hard to decide unfortunately :/ | 16:27:07 |
| leona | I don't think it really makes sense to start ZHF before it's really known what's "really" broken. But we might to have some more days | 16:29:00 |
| vcunat | They might start fixing failures on staging-next 😆 | 16:47:21 |
| 30 Apr 2025 |
|  @fossdd:matrix.org left the room. | 18:30:16 |
| leona | I'll publish a - hopefully good - announcement explaining the situation we're in, and start the ZHF from there. Otherwise time is too limited.. | 20:45:14 |
 Morgan (@numinit) | One of the bits of retrospective from 24.11 said that we should start scaling up our builders pretty soon:
https://discourse.nixos.org/t/nixos-24-11-retrospective/57085 | 20:54:40 |
| leona | To my knowledge thats not really possible / helpful because of the limitations of the hydra scheduler | 20:55:32 |
| Morgan (@numinit) | I have no horse in this race, but was just the notetaker and that reminded me 😀 | 20:55:41 |
| leona | (infra, correct me if i'm wrong) | 20:55:46 |
 Grimmauld (any/all) | current bottleneck is the staging-next of this cycle, which needs K's haskell patches and some darwin love? | 20:57:53 |
| leona | by the default procedure ZHF would start after this cycle's staging-next is merged. I'm not sure what it really needs, but at least it needs 2-3 more days time, if not more. ZHF can also start before, but then we get breaking changes in the ZHF after it started, so not ideal but acceptable | 21:00:01 |
