-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NixOS 24.05 — Feature Freeze & Release Blockers #303286
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
On my side, LLVM is good to go. I would like to get #299807 in but isn't a blocker. If it can get in before the release then that'll be cool. |
Plasma is as good as it's going to be probably, though #300933 would be nice to get in. |
@wegank The only thing regarding NixOS tests that should ideally be sorted before the next release is the situation regarding #303187 and #303150. Should be a minor thing but i consider it important. update: this has been resolved via #303597 |
I would be very disappointed if 24.05 didn't include systemd stage 1 by default, but I do have a lot of work left to make that happen. This issue looks worse than it is. Hopefully I can power this out in the next week or two. Any help would be appreciated. |
I would like to have https://nixos.github.io/amis either linked from the homepage or integrated into the homepage. So that people are aware again that there are AWS AMIs for 24.05! Happy to coordinate with the marketing team on this |
Geospatial software (@NixOS/geospatial) is in pretty good shape, no major changes are required, just regular maintenance. |
I think the Haskell packages are fine since we just updated to GHC 9.6. We will do another round of "remove all broken flags and see how many packages do actually build now" before release, but we have plenty of time for that. |
For the Reproducible Builds initiative in NixOS, I think we are in good shape: for us the only blockers should be issues that prevent reproduction of the minimal iso. While https://github.com/orgs/NixOS/projects/30 does list some of those, the jfsutils nondeterminism seems sporadic and the others have known workarounds or a PR ready (#303436). |
Awesome work. Let's get this work done ... are you able to do this work yourself, or you need some help from the marketing team? The relevant code is here: |
Lisp compilers are good to go 👍 |
No blockers for deepin deepin will release v23 at the end of May, and I plan to port it on 24.11 |
No blockers for all GNOME-adjacent desktop environments I maintain so far, unfortunately I lost track of GNOME 46 update progress and I believe I really need to get around to test all the stuff there. |
We have a blocker for an unknown amount of wrapped python applications which unfortunately is a mass rebuild #302385 |
Lomiri:
Nothing else to report / no other blockers. |
R is good to go 👍 |
Vivaldi browser is currently broken with qt 6: I have a hacky PR which fixes this issue by allowing the user to explicitly opt-into plasma 6: Would be good to fix this properly though, but I am unlikely to do that. |
Beam ecosystem (erlang , elixir...) Has no blockers . |
Yes. Landing #299589 would be important, since I would consider ROCm 6.0 effectively broken without it. If we cannot backport this later I would consider it a blocker. It would be nice it we could also get in get in #298388, to get ROCm working out of the box on more GPUs, since there are users on stable releases, who have opened issues related to that (#302412). |
I would argue that Zig is not ready for release right now. Most importantly, it doesn't build on darwin at all, see #299091, which breaks all packages that depend on it. |
Regarding Nix, we plan on releasing 2.22 next week, and we'd like to have that be the version included in NixOS 24.05 |
We can make it an |
I agree with @RaitoBezarius , I think some time on nixpkgs unstable is warranted to ensure that there's no obvious regressions. (e.g. submodule flake usage broke in 2.20). EDIT: EDIT (@wegank): |
I don't think this is a good idea personally, nix releases historically need time to bake, perhaps like a month of being the unstable to knock out the regressions not caught by people running the development branch (does anyone do that?), and it's too late in the release cycle to make that happen imo. |
Agreed, I was thinking of updating the default LLVM version but it was decided to not do that until after 24.05 for a similar reason. We don't want sudden regressions before a release. Maybe after a release and it isn't backported then that would be fine. |
I had a hope that I might be able to get cctools and ld64 updated for the release, but they’re going to have to wait because the refactoring I’m doing along with the update is too much change this close to the release. I was hoping #301354 could make it, but it’s probably going to have to wait.
Darwin will be updating as well (since the plan after last year’s stdenv work was to do the update annually). If it helps make things easier, I can wait until after Linux is updated. I wouldn’t do the update on Darwin anyway until the 18.1.x update cycle ends to avoid requiring LLVM 18 updates go through staging. |
No blockers for the module system :) Just a brief note regarding |
No blockers for CUDA specifically, but there is a related PR open where a decision needs to be made about the recently introduced EDIT: Cf. a tracking issue for all things CDI that are worth addressing before the release, #290609 |
For python, we are doing a cc @mweinelt for any additional python changes he would like to see as well. |
This is my last involvement with NixOS, so I wish you a very successful 24.05 release. |
Sylabs SingularityCE ( The fix is now available as #306730, but that unfortunately includes behavioral changes and argument/configuration option deprecation. Is it possible to backport a fix like this one with deprecation warnings omitted? |
|
In srvos we still have a list of conditions when we need to disable systemd stage1: https://github.com/nix-community/srvos/blob/a1bbd4ab45c065bb2583f6344f9f72663c683fcb/nixos/common/default.nix#L20 |
Can you remove me from the docs contact? I am no longer the best contact here. |
Lots of improvements on the lua side for this release. There is a big last one pending in staging then I'll need to fix 2/3 of 3 packages for ZHF. |
NixOS 24.05 released! https://discourse.nixos.org/t/nixos-24-05-released/46279 |
Hi, we are Weijia Wang & Jörg Thalheim, the release managers for NixOS 24.05 ("Uakari").
As we approach the next release of NixOS, it's time to discuss the upcoming feature freeze period. We want to ensure that this release is as stable and reliable as possible, and your contributions are crucial to achieving that goal, here are the two upcoming dates in that context:
The complete timeline is available here:
The first restriction will be in place very soon, therefore, we encourage all teams to check in now and mention possible roadblocks, so we get a good overview of what's ahead.
Blockers
Whether you were pinged or not, we encourage everyone to create issues for release blockers and add them to the 24.05 Blockers project.
Check-in
Please comment your status quo and possible issues as soon as possible. We'll check teams once they have checked in.
If you think some subsystem, person or team should be added or removed from this list, update
maintainers/team-list.nix
in time before the next feature freeze announcement.Desktop environments
Platforms
Languages ecosystem
Compilers, build systems
Programs
Modules
Core
Everyone Else
@NixOS/nixpkgs-committers @NixOS/release-engineers
Finally
No issue is too big or too small, but let's remember that we are all working on the project voluntarily in our free time here, so let's focus on issues that can be realistically addressed in the remaining time before the release.
We thank everyone for their contribution!
The text was updated successfully, but these errors were encountered: