| 13 May 2026 |
 vcunat | staging only builds stdenvs | 16:48:31 |
| vcunat | I can stop that immediately easily. | 16:48:42 |
 emily | hmmm | 16:49:06 |
| emily | next cycle would be easier for me timing-wise | 16:49:09 |
| emily | because right now the PRs I have would break update scripts etc. and I'll need to take a day or so to tidy stuff up | 16:49:22 |
| vcunat | I don't really know what will the next staging-next* be, as we will have 3 different candidates. | 16:49:40 |
| vcunat | * I don't really know what the next staging-next* will be, as we will have 3 different candidates. | 16:49:52 |
 hexa | we should probably go for stagingn-25.11 next | 16:50:34 |
| vcunat | Channel-update scripts only come to play after merging staging-next to master. | 16:50:38 |
| hexa | Redacted or Malformed Event | 16:50:38 |
| emily | right. well, I wanted to get the drop in early in the release cycle to avoid wasting a bunch of compute, but just need a couple days to rebase and finish the necessary clean-ups | 16:50:48 |
| vcunat | But that's too late, as we have all binaries at that point. | 16:50:49 |
| emily | I mean actual updateScripts | 16:50:55 |
| hexa | both 26.05 and 26.11 will be topped up with fixes at that point | 16:50:56 |
| emily | many of them will break if x86_64-darwin goes | 16:51:02 |
| emily | I have commits to fix them but they need tidying up and sending out | 16:51:09 |
| emily | non-urgent but I'd prefer to not rush to land stuff with known regressions just for one cycle's difference | 16:51:22 |
| hexa | but we can stop stdenv builds on staging already | 16:51:25 |
| emily | as in staging rather than staging-next? | 16:51:37 |
| hexa | because the next staging-next will be near eom at the earliest | 16:51:41 |
| emily | ah okay | 16:51:53 |
| emily | sorry I misunderstood "current staging" | 16:51:59 |
| emily | (as meaning the current -next cycle wouldn't hit 26.05) | 16:52:14 |
| hexa | it does hit 26.05 | 16:52:26 |
| emily | turning it off in the staging config now sounds totally fine to me yes | 16:52:28 |
| emily | and with ~3d notice before the first 26.11 -next I can have everything for the drop prepared | 16:52:48 |
| vcunat | Well, I can add override on Hydra side to the list of platforms provided by nixpkgs, but maybe... we'd better just change the list on nixpkgs side? (on the staging branch) | 16:53:36 |
| hexa | preparing that change for staging right now | 16:53:47 |
| hexa | I'd rather not do it on hydra | 16:54:21 |
| vcunat | And doing that... you can pull it out of the big jobset as well in the same way. | 16:54:26 |
