| 15 May 2026 |
 kuflierl | * Sooo, i made a mistake while merging https://github.com/NixOS/nixpkgs/pull/515479 and the version in the attr-name is wrong. I suggest merging https://github.com/NixOS/nixpkgs/pull/520658 in order to remove the offending version from the attr-name. The change should not cause any rebuilds. | 23:46:55 |
| 16 May 2026 |
|  same joined the room. | 10:49:54 |
| same | hey! quick question: i see that the dates in the schedule on pr 503391 were edited; should pr 516381 be updated accordingly? i'd edit it myself but i don't have permissions | 11:24:56 |
 hexa | yes, correct. will happen in a minute. | 11:28:40 |
| hexa | rm poked | 11:28:49 |
 yaya | thanks for the hint! | 13:26:41 |
| 17 May 2026 |
 Grimmauld (any/all) | https://github.com/NixOS/nixpkgs/pull/521022#pullrequestreview-4304200622
Technically this is a change in behavior, pointing a path to a runtime-mutable config from /etc to /var/lib.
It was broken before and never really worked properly, which is why the fix here is imo non-breaking. However, it is still a change in behavior. Does this need a breaking changes exception? Do i just wait for branch-off? The change of the PR is overall just necessary and much-needed cleanup, and i'd really hate to block on a technicality, but i also don't want some release manager to come chew me out for merging stuff after freeze i shouldn't merge. | 12:06:38 |
| yaya | Reviewed the PR and agree with having it merged with a release note. | 16:07:09 |
| Grimmauld (any/all) | thanks! | 16:08:42 |
 emily | are we okay to land non-backwards-incompatible deprecation warnings? (context: https://github.com/NixOS/nixpkgs/pull/521144) | 19:39:04 |
 Sandro | might be a little late, but the change itself is very good | 19:43:27 |
| Sandro | * might be a little late, but the change itself is very good as nested lists IIRC break cross or something closely related | 19:43:44 |
| Sandro | * might be a little late, but the change itself is very good as nested lists IIRC break cross | 19:43:53 |
| emily | plausible, they don't handle e.g. getDev | 19:44:00 |
| emily | re late, I figure the main deadline for warnings is ~branch-off as they can't break anything by themselves and branch-off is when people might be doing early testing to see if there's any issues they'll need to handle | 19:44:32 |
| emily | but will defer to RMs for sure :) | 19:44:35 |
| yaya | agreed. I leave it up to you to merge :) | 22:37:28 |
| 18 May 2026 |
 h0nig2k | Hi, my 2 cents around the current release: can we have a "26.10.5"-like release next time (preponement of release date)? it is the second release which comes with a week of delay. I highly appreciate NixOS and the release managers, just feedback i can share. For example: consumption of a fresh NixOS start of december / christmas is not nice, given that people are on vacation. In case of delays, the consumption and adoption is becoming hard during christmas. | 13:34:09 |
| hexa | Releases are scheduled in May and November so we have time to land KDE and GNOME updates. | 13:36:22 |
| hexa | see also https://github.com/NixOS/rfcs/blob/master/rfcs/0080-nixos-release-schedule.md | 13:37:40 |
 Sigmanificient | "polished experience for 60,000+ packages" 🥺 | 13:38:23 |
| Sigmanificient | Nixpkgs has grown so much since | 13:38:37 |
| Sigmanificient | 143734 entry in packages.json | 13:39:00 |
 leona | And actually it doesn't come with a week of delay. We schedule for a week before the end of the month so we can release within the month. Here, there a scheduling problems because of the work hydra.nixos.org does. Hopefully we can improve its capacity sometime in the future. | 13:40:48 |
 jopejoe1 | We also explilictly moved the planned a release date some days before the end of the month, so that if some comes up, we would still have a buffer to release it in the month corresponding to the release versikn. | 13:41:02 |
| jopejoe1 | * | 13:41:09 |
| jopejoe1 | * | 13:41:34 |
| leona | There were quite some releases that released in December (the 35th November) ;) | 13:41:38 |
| jopejoe1 | * | 13:41:48 |
| leona | There are some discussions of supporting releases longer, but tbh in the current state of the community and infra we probably cannot do this right now | 13:42:20 |
