Skip to content
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.11 - Feature Freeze & Release Blockers #344920

Closed
25 of 40 tasks
RossComputerGuy opened this issue Sep 27, 2024 · 42 comments
Closed
25 of 40 tasks

NixOS 24.11 - Feature Freeze & Release Blockers #344920

RossComputerGuy opened this issue Sep 27, 2024 · 42 comments
Labels
5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems 6.topic: release process Issues or PRs which are parts of the NixOS release process

Comments

@RossComputerGuy
Copy link
Member

RossComputerGuy commented Sep 27, 2024

Hello, this is your NixOS 24.11 ("Vicuna") release managers, Tristan Ross & Weijia Wang.

Today we're glad to announce the kickoff of the release schedule. Because of that, it's time to discuss the feature freeze. NixOS releases have had a history of being stable and reliable and we would like to continue that. I would like to also point out that if there's any issues with the aarch64 platforms, that we could get those fixed or any other improvements done.

Some important dates of concern:

  • 2024-10-11: Restrict breaking changes to Release Critical Packages
  • 2024-10-25: Restrict all breaking changes: allow only non-breaking updates and Desktop Manager changes

Our full 24.11 release schedule is available here

As of the time of posting this, we have a couple weeks before the release critical changes are restricted. If at all possible, let's get those done as soon as possible.

Blockers

If you were pinged or know of any blocking issues for NixOS 24.11, please submit them in the issue tracker and place them into the 24.11 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

  • Darwin: @NixOS/darwin-maintainers

Languages ecosystem

Compilers, build systems

Programs

Modules

  • ACME: @aanderse @arianvp @emilazy @flokli @m1cr0man
  • systemd: @NixOS/systemd

Core

  • Docs: @NixOS/documentation-team
  • Marketing: @garbas @tomberek
  • Module system: @infinisil @roberth
  • Nix/nix-cli ecosystem: @NixOS/nix-team
  • NixOS tests: @tfc

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!

@RossComputerGuy RossComputerGuy added the 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems label Sep 27, 2024
@RossComputerGuy
Copy link
Member Author

RossComputerGuy commented Sep 27, 2024

More pings since GitHub limits the amount of pings, please refer to the original issue for the checkboxes

Modules

Core

@K900
Copy link
Contributor

K900 commented Sep 27, 2024

Plasma is waiting for the staging-next cycle, and then the 6.2 release in two weeks (2024-10-08 target), the beta builds and is usable on #341487, there will probably need to be some last minute changes for the final release.

Edit: Qt 6.7.3 also finally released today, I'll try to get it into this cycle.

@emilazy
Copy link
Member

emilazy commented Sep 27, 2024

The primary Darwin blocker is Randy’s SDK rework, which is targeted for the next staging cycle and critical to the health of the platform. It will significantly reduce the burden of supporting macOS, both for the core Darwin maintainers and packagers of any software that works on it, and although it is mostly compatible, it still requires significant changes to the Darwin standard environment and some API deprecations. Missing 24.11 would be devastating for backports, especially as more and more packages are starting to require newer SDKs that we don’t currently have packaged, but thankfully the work is on track and has already been very well‐tested, so I expect it to be merged relatively uneventfully.

@NickCao
Copy link
Member

NickCao commented Sep 27, 2024

Plasma is waiting for the staging-next cycle, and then the 6.2 release in two weeks (2024-10-08 target), the beta builds and is usable on #341487, there will probably need to be some last minute changes for the final release.

Edit: Qt 6.7.3 also finally released today, I'll try to get it into this cycle.

Qt 6.8 is also targeting a 2024-10-08 release, I'd prefer getting that in.

@K900
Copy link
Contributor

K900 commented Sep 27, 2024

I would not want to risk a Qt bump in the last staging cycle of the release. We can get it in post release.

@jbedo
Copy link
Contributor

jbedo commented Sep 27, 2024

For R a significant portion of the package tree is broken due to some packages explicitly enabling http support in libxml2 (notably gdal and libspatialite). The overriding results in multiple versions of libxml in the closure of some packages and causes subsequent loading issues. Not sure what the solution here is.

@mweinelt
Copy link
Member

Python has done the necessary migration to the 3.12 release track early in the development cycle, so we don't have any blockers at this time.

@stigtsp
Copy link
Member

stigtsp commented Sep 27, 2024

Perl 5.40.0 is in staging-next at the moment. A mass update for perlPackages should begin soon, and hope to get that done for 24.11.

@ElvishJerricco
Copy link
Contributor

This is not essential, but I've been hoping to get systemd initrd enabled by default for this release. Here's the blockers for that:

Other than that, I think it's good to go. Please let me know if you have any other problems with it. I intend to fix the above issues in the next week or two.

We can delay this till after 24.11, which would make things easier. But that would be very disappointing IMO.

@happysalada
Copy link
Contributor

No blockers in the beam ecosystem

@Mic92
Copy link
Member

Mic92 commented Sep 28, 2024

Blockers in C, are the mentioned macOS sdk updates. I changed the responsible people for the "nix-cli" to the Nix team, since I have been involved in that bit lately a bit. I don't think there are any blocker on that level. Rust also should be fine.

@Mic92
Copy link
Member

Mic92 commented Sep 28, 2024

I think we can remove the "Marketing" checkmark from the template. I don't think they do have any release blocker related items. Website updates are handled by NixOS release manager except for the final merge.

@hraban
Copy link
Member

hraban commented Sep 28, 2024

All quiet on the lisp front. 👍

@Gabriella439
Copy link
Contributor

No blockers for Dhall

@wineee
Copy link
Member

wineee commented Sep 28, 2024

No blockers for DDE

@katexochen
Copy link
Contributor

katexochen commented Sep 29, 2024

Go blockers (only common maintenance tasks, will be ready in-time):

@m1cr0man
Copy link
Contributor

m1cr0man commented Oct 2, 2024

No ACME blockers, but we do have some PRs related to the test suite. To get pebble up to 2.6.0 we needed to change some of the assertions. I also have an open change which hopefully makes the tests less flaky

@siriobalmelli
Copy link
Contributor

Foundationdb is currently still broken (#319537 - since 24.05).

I'd love some help getting this sorted and/or moving from foundation 7.1 to 7.3.

Happy to pitch in, just over my head and missing a bit of direction 🙏

@teto
Copy link
Member

teto commented Oct 2, 2024

No lua blocker.

@reckenrode
Copy link
Contributor

The Darwin rework is here:

@fgaz
Copy link
Member

fgaz commented Oct 8, 2024

If possible I'd like for Tcl to become a language ecosystem / package set before 24.11 to make backports easier:

@raboof
Copy link
Member

raboof commented Oct 8, 2024

If we can't fix #345329 then we likely will not have a reproducible minimal iso for this release. That would be sad but realistically I don't think it should be a blocker.

@imincik
Copy link
Contributor

imincik commented Oct 8, 2024

@NixOS/geospatial doesn't have any blockers.

Following PRs would be nice to have in 24.11:

@vbgl
Copy link
Contributor

vbgl commented Oct 9, 2024

No blocker for Coq.

No blocker for OCaml.

@romildo
Copy link
Contributor

romildo commented Oct 9, 2024

No block for Enlightenment, Lumina, and LXQt.

@thecaralice
Copy link
Contributor

Would be nice to get #300532 merged since it apparently affects a lot of projects yet is stale for some reason.

@RossComputerGuy
Copy link
Member Author

As per the release schedule, all release critical packages are blocked.

@OPNA2608
Copy link
Contributor

Lomiri DE

Should be fine. There'll be another minor OTA release later this month that might come with some more component bumps. Will check for relevant changes & bump/backport when it happens, not expecting anything serious though.

@K900
Copy link
Contributor

K900 commented Oct 13, 2024

Plasma 6.2 is good to go on master now, and given how long the staging cycle was, we also squeezed in Qt 6.8, which seems to be fine so far, and a big improvement on 6.7 in terms of Wayland stability. I think this was the right call after all.

@Aleksanaa Aleksanaa pinned this issue Oct 15, 2024
@SigmaSquadron
Copy link
Contributor

SigmaSquadron commented Oct 17, 2024 via email

@ulrikstrid
Copy link
Member

Plasma 6.2 is good to go on master now, and given how long the staging cycle was, we also squeezed in Qt 6.8, which seems to be fine so far, and a big improvement on 6.7 in terms of Wayland stability. I think this was the right call after all.

This broke packages relying on pyqt6, we have a interim-solution in master now but it could break any day since the package url isn't stable. If possible we should wait for a release of pyqt6 that is compatible and package that.

@K900
Copy link
Contributor

K900 commented Oct 17, 2024

We're not holding back a release for PyQt. They still have over a month, hopefully they get their stuff together.

@arianvp
Copy link
Member

arianvp commented Oct 20, 2024

I would like to get #343939 in before the release.

@ulrikstrid
Copy link
Member

We're not holding back a release for PyQt. They still have over a month, hopefully they get their stuff together.

As long as there's a decision I don't mind, I'm not a stable-user anyway

@minijackson
Copy link
Member

Can I ask for help getting #331750 reviewed / merged before the 25th? It already has two major bumps

@tomodachi94 tomodachi94 added the 6.topic: release process Issues or PRs which are parts of the NixOS release process label Oct 24, 2024
@Eveeifyeve
Copy link
Contributor

Eveeifyeve commented Oct 26, 2024

I mean nim might be a blocker. Unfortunately I made some mistakes in a pr that caused a brunch of issues like high cpu usage and etc. More about at issue #350913. Just confirming its a nix problem, not a nim problem.

@ehmry
Copy link
Contributor

ehmry commented Oct 28, 2024

Nim has been taken care of.

@sternenseemann
Copy link
Member

sternenseemann commented Nov 1, 2024

Regarding Ada, I've been working on updating all packages released by AdaCore to their 25.0.0 version: #352856. This would get rid of the dependency on Python 3.9, but I don't think that's a priority for 24.11?! Unfortunately that causes quite a few undiagnosed regressions. Consequently, I don't think this is a good fit for 24.11.

What we could do for 24.11, is upgrading the default gnat version to 13 to match gcc: #352894.

Edit: Done.

@Artturin Artturin unpinned this issue Nov 3, 2024
@Artturin Artturin pinned this issue Nov 3, 2024
@Artturin
Copy link
Member

Artturin commented Nov 3, 2024

Misvimiumclick

@ShamrockLee
Copy link
Contributor

I hope to bump libchewing onto a stable version (#314538). This package is the basis of Chewing Input Method on all IM frameworks and is crucial for zh-TW users.

@ShamrockLee
Copy link
Contributor

ShamrockLee commented Nov 11, 2024

The package conan currently builds on the master branch with the official binary substituter but fails some PyTest tests with the --rebuild flags.

Is it safe to introduce a change that would cause conan to rebuild during the ZHF period? (See also #354811 for the discussions.)

Update: Fixed by disabling the flaky test.

@JohnRTitor JohnRTitor unpinned this issue Nov 15, 2024
@RossComputerGuy
Copy link
Member Author

We released! https://discourse.nixos.org/t/nixos-24-11-released/56811

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems 6.topic: release process Issues or PRs which are parts of the NixOS release process
Projects
None yet
Development

No branches or pull requests