| 5 May 2024 |
|  westexjeff changed their profile picture. | 18:38:38 |
| 6 May 2024 |
 Weijia | ZHF: https://github.com/NixOS/nixpkgs/issues/309482 | 07:42:02 |
 Vladimír Čunát | The staging-next that's starting now (link) can still contain general "breaking changes", given they were only disallowed a few days ago. But I hope it won't impact ZHF that much. | 07:47:35 |
 pbsds | I see no obvious place to set aside PRs that introduce breaking changes for later.
How do you feel about introducing a status: blocked until branch-off label? | 11:07:48 |
 Alyssa Ross | wouldn't it be better to just have a branch? | 11:29:01 |
| pbsds | Retargeting a bunch of pulls to that branch, and merging that branch into master post 24.05 branch-off strikes me as more work
| 11:44:25 |
 hexa | also CI relies on things getting cached, while that branch would rot for 2-3 weeks 🤔 | 11:44:56 |
| Alyssa Ross | no worse than staging often is | 11:45:10 |
| hexa | yeah, but staging is … not great 🙂 | 11:45:34 |
| Alyssa Ross | the nice thing about it would be that PRs can be completed, rather than staying in a zombie state for weeks | 11:45:36 |
| Alyssa Ross | but don't let me stop you doing a lobal | 11:45:59 |
| Alyssa Ross | either would be better than nothing | 11:46:10 |
| Alyssa Ross | I'd even like branches for future releases tbh, to handle stuff like turning deprecation warnings into hard errors, so you don't have to remember to come back in 6 months | 11:46:31 |
| Alyssa Ross | I missed my opportunity to remove some APIs in 24.05 that I'd planned to | 11:46:44 |
| pbsds | i believe there usually is a board in https://github.com/orgs/NixOS/projects where todos for the next release can be added. One for 24.11 should pop up once 24.05 is tagged | 11:55:10 |
|  Charles changed their display name from Charles ⚡️ to Charles. | 17:01:07 |
 Arian | I'm wondering if we need a "Release Criticial Modules" list too in future releases: https://nixos.github.io/release-wiki/Release-Critical-Packages.html
I'd add systemd, dbus and switch-to-configuration to them given the mess I caused with dbus-broker revert :') | 19:49:21 |
| 7 May 2024 |
|  riotbib joined the room. | 12:09:57 |
| riotbib | knock … I'm back | 12:10:10 |
| riotbib | could someone change the topic to 24.05 "Uakari"? | 12:11:08 |
| riotbib | (this is lennart, I regained access to my old Matrix account) | 12:11:46 |
| Weijia changed the room topic to "24.05 "Uakari" | https://nixos.github.io/release-wiki/Home.html" from "23.11 "Tapir" | https://nixos.github.io/release-wiki/Home.html". | 12:11:56 |
| 10 May 2024 |
 ma27 | so I just realized that postgresql12 will be EOL on nov 14 which is within the supported range of 24.05. opinions on removing/keeping it? we're past the breaking change restriction of may 1 already.
also am I right with my interpretation of https://github.com/NixOS/nixpkgs/issues/303285 that current staging will be merged into staging-next and that's the second staging cycle for 24.05? asking for a few postgresql updates. | 09:10:05 |
| hexa | we have on staging cycle remaining before branch-off | 09:13:55 |
| hexa | * we have one staging cycle remaining before branch-off | 09:14:00 |
| hexa | and I'm pro removal of postgresql12 🙂 | 09:14:39 |
| Alyssa Ross | oh right — do package removals count as breaking changes? I have a couple I've been holding off on merging because I wasn't sure. | 09:49:13 |
| Vladimír Čunát | I'd say they do, at least if the packages worked, etc. (there will be some gray cases surely) | 09:51:54 |
| Weijia | I guess yes, but I won't block them if they're considered pre-release cleanups. | 09:52:33 |
| Weijia | https://nixos.github.io/release-wiki/Feature-Freeze-Announcement.html#pre-release-cleanup | 09:52:52 |
