| 10 Jun 2025 |
 Arian | Fastly can purge yes | 11:49:04 |
| Arian | https://github.com/NixOS/infra/pull/727/files hypothetical proposal | 12:30:41 |
 emily | heads up – https://github.com/NixOS/nixpkgs/pull/415566 we're expecting on the Darwin team end that we'll want to turn off x86_64-darwin on the jobsets sometime between after 26.05 branch-off and the release of 28.11, most likely after either 26.05 or 27.05 branch-off | 13:06:07 |
| emily | (if it's around branch-off, then for the unstable branch only of course, until the end of the support period for the branched-off release) | 13:06:38 |
 Vladimír Čunát | That will help staging* iterations quite a bit, I expect. | 13:12:27 |
| emily | indeed | 13:12:47 |
| Vladimír Čunát | Though it's not very soon yet. | 13:12:58 |
| emily | Darwin might stop being the bottleneck if we have twice the AArch64 build capacity and don't need any Intel :P | 13:13:06 |
| Vladimír Čunát | (so relative bottlenecks might change in the meantime) | 13:13:18 |
| emily | right. well, we could of course just decide to drop it any time, but start of 26.11 cycle seemed like the earliest natural point | 13:13:52 |
| emily | based on the limited stats I can find and the resources trade-off I personally don't think it makes sense to wait longer than that, but didn't want to pre-commit to an exact point immediately | 13:14:44 |
| Vladimír Čunát | By natural point you mean Apple dropping support in macOS or rosetta2? | 13:15:36 |
| emily | I assume that even just having it only be used on stable for six months will help, since there are fewer rebuilds there | 13:15:42 |
| emily | well, 26.11 release will be shortly after the first macOS version that doesn't run on Intel comes out. 27.11 will be shortly after the first macOS version that we can't use to build for x86_64-darwin comes out. 28.11 will be shortly after end of security support for the last macOS version to run on Intel. so all of those are "natural points" in a sense. | 13:17:24 |
| emily | and if we're dropping it for a release we should surely drop it right after branch-off for that release, to not waste half a year building binaries we won't ship | 13:17:57 |
| emily | (Darwin users do get defaulted to nixpkgs-unstable by the installer, so it would be a little weird for half a year, but it'd at least be a single-command fix for the final ~seven months of support.) | 13:19:06 |
