Open zimbatm opened 7 months ago
Fully agree with the issue :)
Not sure about a good solution though. I don't think having the Nix team as CODEOWNER would help as we do releases when we think they are ready, and we probably wouldn't catch more regression just by doing the Nixpkgs update ourselves.
Something about some better hydra checks would help a lot indeed (related: https://github.com/NixOS/nix/issues/9741, https://github.com/NixOS/nix/issues/9744, https://github.com/NixOS/nix/issues/9743). It wouldn't be perfect since Hydra isn't meant to change the Nix version used, so the only tests that might exert the new Nix will be the tests that run Nix in a VM. But still much better than what we have right now.
@roberth has done a lot of deep diving into this recently.
Ok. Let me know if you need anything from the infra team.
Just discussed that during the Nix maintainers meeting today:
Sweet! By the way, GitHub recently doubled the number of resources on the runners, and also now supports nested virtualization.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/2024-01-19-nix-team-meeting-minutes-116/38837/1
Is your feature request related to a problem? Please describe.
Whenever the Nix team releases a new version, it takes a while for nixpkgs to catch up. At the same time, nixpkgs often finds regression in Nix that would have been good to know before cutting a release. Something is missing in the process to make that smoother.
Describe the solution you'd like
I'm not set on something specific. Here are some ideas:
Priorities
Add :+1: to issues you find important.