| 21 Nov 2025 |
 ners | I once ran a ZHF that was after the release. We then joked that we're participating in the next ZHF very early. 🙃 | 08:11:20 |
| ners | * I once ran a ZHF that was just a few days after the release. We then joked that we're participating in the next ZHF very early. 🙃 | 08:11:35 |
| ners | Fixes are aways good to get in. | 08:11:38 |
|  jappie joined the room. | 17:02:07 |
| 22 Nov 2025 |
|  Quirin Brändli joined the room. | 00:03:45 |
| Quirin Brändli | I got a quick question just out of curiosity:
While the feature freeze time was ongoing, the full master branch was frozen for 3 weeks, right? That means that nixos-unstable was frozen as well, right? | 00:05:27 |
 hexa | nothing is frozen | 00:21:59 |
| hexa | it is open for fixes and non-breaking changes | 00:22:07 |
| hexa | nixos-unstable also gets built during feature freeze | 00:22:28 |
 Grimmauld (any/all) | That, and not all fixes that look non-breaking are actually non-breaking. Updates always have the potential to cause regressions in downstream packages, it is on the maintainers to estimate the probability of that and weigh that against maintenance burden in the coming release cycle.
E.g. it is possible to have the choice between a risky update on an important package, or be stuck doing security backports for half a year. You then ask release managers laying out the problem and how bad you think fallout will be, and it is a judgment call. But these things do go wrong occasionally, which means even during freeze month we get regressions | 07:55:51 |
 VladimÃr ÄŒunát | Yeah, every change breaks someone's workflow
https://xkcd.com/1172/ | 07:59:57 |
| Grimmauld (any/all) | I was more thinking libxml 2.15 (libxml is notorious to break shit, but I really do not want to manually maintain 2.14.x for half a year). Or sdl3/sdl2-compat, where a harmless looking update (they were always very tame in the past) currently causes dwarf fortress to segfault on launch. | 08:01:53 |
| Grimmauld (any/all) | Neither of the two is spacebar heating. Its gambling, where the risky libxml update surprisingly didn't break barely anything, and the safe-looking SDL update causes issues. And none has the knowledge to know that in advance, maintainers can only guess and will guess wrong. | 08:03:42 |
| VladimÃr ÄŒunát | Yes, I know. I wasn't being serious 🙂 | 08:16:57 |
|  @chaotic-routine:matrix.org joined the room. | 23:13:45 |
| @chaotic-routine:matrix.org left the room. | 23:16:31 |
| 23 Nov 2025 |
|  dave :3 set a profile picture. | 16:53:40 |
 eveeifyeve | Any chance to update and remove nim1 from this release or am I late? | 20:27:21 |
 leona | You said, that nim1 is still in LTS, I don't see the reason to urge with that knowledge. Otherwise I can only repeat what I already said: We don't want to ship outdated software that does not get patches, this includes when nobody wants to maintain them in Nixpkgs
We're quite close to the release, though. | 21:57:12 |
| 24 Nov 2025 |
|  whispers (it/fae) joined the room. | 00:27:59 |
|  Phobos joined the room. | 03:34:30 |
|  aleksi joined the room. | 10:14:42 |
|  Grimmauld (any/all) joined the room. | 12:45:48 |
| leona | branch-off finished this time without breaking master 😂 | 20:45:09 |
 misuzu | There're lint error in CI for nixos/release.nix file:
https://github.com/NixOS/nixpkgs/actions/runs/19648579852/job/56269795501?pr=464694
| 20:46:27 |
| misuzu | There's lint error in CI for nixos/release.nix file:
https://github.com/NixOS/nixpkgs/actions/runs/19648579852/job/56269795501?pr=464694 | 20:48:21 |
| leona | 🙃 | 20:51:55 |
| leona | I shouldn't have said that... | 20:52:01 |
| leona | Redacted or Malformed Event | 20:56:20 |
| leona | https://github.com/NixOS/nixpkgs/pull/464697 | 20:56:27 |
