| 22 Apr 2025 |
 emily | hopefully will be able to sort it out in the next 36 hours, yes. | 22:07:18 |
 leona | Time zones are super confusing and I don’t want to make anyone angry about 24 hours so that’s why I decided to it this way. I will think about better wording, also for the release wiki | 22:08:34 |
| leona | For most of the days it’s pretty irrelevant anyways, just for the freezes | 22:09:11 |
| emily | yes, for sure, timezones are a mess | 22:11:52 |
| emily | "something is okay if it's the last day it's meant to be allowed anywhere on the planet" is a sensible general principle, I think. the problem is that if something becomes allowed on a certain date, then "anywhere on Earth" is no longer one timezone but two, since you want the earliest possible date for that :) | 22:12:52 |
| emily | IIRC the schedule used to just be UTC? which I guess trades global convenience for increased legibility. | 22:13:23 |
| emily | anyway… in practice it doesn't matter too much since all breaking stuff going into staging is only actually going to start hurting days from now :) but I didn't want to let the deadline pass without saying something | 22:14:09 |
| emily | thanks for taking care of the release | 22:14:22 |
| 24 Apr 2025 |
 Arian | I want to drop the amazonImage job from the release blockers 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:10:31 |
| 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 |
 Vladimír Čunát | 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 |
