| 11 Apr 2024 |
 jonringer | For what it's worth, I think you did a great job figsoda . Take some time, you deserve it :) | 01:50:13 |
| jonringer | Weijia: not sure when you want to meet, but I think it would be good to come up with the release schedule and plan the next steps up until ZHF. | 01:52:00 |
| jonringer | figsoda: don't forget about release editor as well :) | 01:52:13 |
 figsoda | In reply to @jonringer:matrix.org
figsoda: don't forget about release editor as well :) Would you mind picking the release editors for me? I asked alejandrosame and they would be busy during 24.05, so we would need 2 new release editors. Thanks! | 01:53:57 |
| jonringer | ajaxbits, jacg, and krbylit all aplied. Unfortunately not super familiar with any of these candidates | 01:55:12 |
| jonringer | * ajaxbits, jacg, and krbylit all aplied. Unfortunately not super familiar with any of these candidates. https://discourse.nixos.org/t/24-05-call-for-release-manager-editor/42195/11 | 01:55:30 |
| figsoda | In reply to @jonringer:matrix.org
ajaxbits, jacg, and krbylit all aplied. Unfortunately not super familiar with any of these candidates. https://discourse.nixos.org/t/24-05-call-for-release-manager-editor/42195/11 westexjeff (https://matrix.to/#/!aGqRytqbCECitOFhbt:nixos.org/$GnT-XdIIqbrSOzzEByKLVWy89cH6kEgwVPG-bAucm6U?via=nixos.org&via=matrix.org&via=helsinki-systems.de) and PowerUser64 (https://matrix.to/#/!aGqRytqbCECitOFhbt:nixos.org/$PzR-5xypmsQFPbnMGrUlUZBiyJ7YRelAJb_ftosHk9U?via=nixos.org&via=matrix.org&via=helsinki-systems.de) seems to also be interested | 01:58:08 |
| jonringer | Aw yes, thank you | 02:00:30 |
| jonringer | * westexjeff, PowerUser64 ,ajaxbits, jacg, and krbylit all aplied. Unfortunately not super familiar with any of these candidates. https://discourse.nixos.org/t/24-05-call-for-release-manager-editor/42195/11 | 02:02:05 |
 Weijia | In reply to @jonringer:matrix.org
Weijia: not sure when you want to meet, but I think it would be good to come up with the release schedule and plan the next steps up until ZHF. Probably this Saturday or Sunday evening in UTC+2? I'm counting 7 hours of time difference between us. | 02:27:14 |
|  rick.special joined the room. | 02:32:40 |
|  danielrf joined the room. | 02:38:33 |
 PowerUser64 | Weijia: I'm on PDT, which is UTC-7 right now. If you schedule a meeting, feel free to ping me and tell me when it is. I'll be fairly busy the next few days, but I'll be more available closer to and after the end of this month. What's our timeline for 24.5? | 04:04:06 |
| Weijia | https://nixos.github.io/release-wiki/Release-Process.html | 04:10:50 |
| Weijia | We're almost -7 weeks from release, so probably should start the first event asap | 04:12:02 |
| jonringer | I was expecting to go through 4.1 and 4.2 together https://nixos.github.io/release-wiki/Once-Appointed.html | 04:14:25 |
| jonringer | a lot of the "work" is pretty "copy, update, paste". If you feel confident to do it on your own, feel free to do so. Otherwise we go through it together | 04:16:06 |
| jonringer | * a lot of the "work" is pretty "copy, update, paste". If you feel confident to do it on your own, feel free to do so. Otherwise we can go through it together | 04:16:26 |
| Weijia | Feature freeze announcement: https://github.com/NixOS/nixpkgs/issues/303286 | 06:17:47 |
 Randy Eckenrode | I assume cctools/ld64 would fall under binutils. Where does bumping the effective minimum version on Darwin fall on the breaking scale? The cctools/ld64 update may require a bump to 10.14 as the effective minimum version for building things. | 16:09:22 |
| Weijia | In reply to @reckenrode:matrix.org
I assume cctools/ld64 would fall under binutils. Where does bumping the effective minimum version on Darwin fall on the breaking scale? The cctools/ld64 update may require a bump to 10.14 as the effective minimum version for building things. I think I'd ask for an x86_64-darwin jobset (and a public announcement) before approving a PR on this, even if it only contains a treewide substitution of "10.12" by "10.14" | 16:47:08 |
| jonringer | 10.14 is kind of "big" for macOS, C++14 (IIRC), and a few other tooling improvements landed in that release | 16:48:48 |
| jonringer | However, it was released in Sept 2018, so I think ~5 years is a pretty low bar | 16:49:20 |
| Randy Eckenrode | In reply to @wegank:matrix.org
I think I'd ask for an x86_64-darwin jobset (and a public announcement) before approving a PR on this, even if it only contains a treewide substitution of "10.12" by "10.14" It’s not an SDK change. That will come post 24.05. The updated cctools and ld64 have a hard requirement on using libdispatch APIs that are only available in 10.14. They can be built with the 11.0 SDK and a 10.14 deployment target in the meantime until the default SDK is changed. | 16:49:37 |
| Randy Eckenrode | In reply to @jonringer:matrix.org
10.14 is kind of "big" for macOS, C++14 (IIRC), and a few other tooling improvements landed in that release We use our own libc++, so even 10.12 has whatever the latest is. This ld64 update would bring Darwin up to the version of ld-classic shipped in Xcode 15.3. The cctools update handles signatures better. If it’s a linker-signed ad hoc signature, strip&c will update the signature automatically without a hook or wrapper. | 16:52:12 |
| Weijia | In reply to @reckenrode:matrix.org
It’s not an SDK change. That will come post 24.05. The updated cctools and ld64 have a hard requirement on using libdispatch APIs that are only available in 10.14. They can be built with the 11.0 SDK and a 10.14 deployment target in the meantime until the default SDK is changed. Wait, with the 11.0 SDK on x86_64-darwin? | 16:52:18 |
| Randy Eckenrode | In reply to @wegank:matrix.org
Wait, with the 11.0 SDK on x86_64-darwin? Yes. overrideSDK can build with one SDK and set an earlier deployment target. Fixing that was one of the goals of the rewrite in staging. | 16:53:10 |
| Randy Eckenrode | Darwin already has two other packages in the bootstrap that require the 11.0 SDK to build: psutil and libuv. cctools and ld64 would be the first to require a newer version at runtime. | 16:54:07 |
 Vladimír Čunát | You don't plan dropping x86_64-darwin anytime soon, I guess? | 16:58:39 |
| jonringer | Just to reason about time left, breaking changes to staging need to land by May 1st, to allow for some stabilization iterations before cutting the release. If we are signing up for a blocker, it should be able to fit within that time period (or very close to that time period). | 17:00:56 |
