| 18 Apr 2025 |
 tgerbet | As a pre notification I'm likely to request an exception to BC change restriction for nginx next week.
NixOS and nginx release are aligned in May and they plan to start their new cycles next week https://mailman.nginx.org/pipermail/nginx/2025-April/F4F33YXMJPZMQ4VKG3WJPNGSIEFFBMKX.html
Not bumping means we will have to maintain EOL nginx versions which is not great. | 18:30:48 |
 leona | ack, ok! | 18:31:31 |
| 19 Apr 2025 |
|  jopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 (4094@eh22). | 13:01:20 |
| 21 Apr 2025 |
|  gerryd joined the room. | 15:24:59 |
| 22 Apr 2025 |
 emily | leona: requesting potential freeze exemption for https://github.com/NixOS/nixpkgs/pull/400646 (and its dependency https://github.com/NixOS/nixpkgs/pull/400427), and https://github.com/NixOS/nixpkgs/pull/397398. (because my test build of the latter is running into some unrelated-looking diffutils build issue and I don't know that I'll have the time to investigate tonight, and I'd like to understand https://github.com/NixOS/nixpkgs/pull/400739 a little better before hitting the button on the libGL one). I project minimal impact since these are mostly just deprecations and fixes that could technically break someone doing something incredibly bizarre. | 22:01:48 |
| emily | (actually, I'm not sure if we're already meant to be in the freeze, because it's already the 23rd in anywhere-on-Earth time, but I've been interpreting the intent as "once it is no longer the 22nd anywhere on Earth") | 22:03:36 |
| emily | * ( actually, I'm not sure if we're already meant to be in the freeze, because it's already the 23rd in anywhere-on-Earth time, but I've been interpreting the intent as "once it is no longer the 22nd anywhere on Earth" never mind, inverted the sign in my head 🫠) | 22:04:30 |
| leona | For this time I intend it to be 23rd AoE end of day, i.e. in about 36 hours I think | 22:05:46 |
| leona | If it’s still a problem then, I can have a more in depth look, but it seems okay for me | 22:06:43 |
| emily | aha, okay. I'd expect "2025-04-24 – Restrict all breaking changes" for that (rather than -23), but that's the release wiki's fault 😅 | 22:07:09 |
| 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 |
