| 15 Nov 2021 |
 sterni | * oh no it has been re-enabled it seems~~, nevermind has recurseForDerivations = false | 17:50:34 |
 Vladimír Čunát | master..r-updates isn't empty anyway. | 17:50:48 |
 hexa | In reply to @jonringer:matrix.org
When do we want to start the next staging PR? would be kind to ping before opening, so we can get some last minute things in 🙂 | 17:50:54 |
| sterni | Vladimír Čunát: yeah, but due to staging-next it is a full rebuild, otherwise I suspect some cache would still be valid… | 17:51:25 |
| sterni | but supposedly r builds are fast… https://github.com/NixOS/nixpkgs/commit/ccd1029f58a3bb9eca32d81bf3f33cb4be25cc66 | 17:51:49 |
| sterni | Vladimír Čunát: jbedo hangs out in nixos dev, in case we want to coordinate queue issues | 17:53:42 |
 jonringer | In reply to @sternenseemann:systemli.org
but supposedly r builds are fast… https://github.com/NixOS/nixpkgs/commit/ccd1029f58a3bb9eca32d81bf3f33cb4be25cc66 maybe, but 40k fast builds is still 40k builds. Same can be said about a lot of python builds | 17:57:05 |
| sterni | indeed, I don't think it came quite across as a snarky comment | 17:58:21 |
| jonringer |
so we can get some last minute things in 🙂
Sure, but this cycle is already ~3 days late
| 17:58:18 |
| jonringer | Oh, I just meant that it's still "build pressure", and it's concerning if I want to start another staging-next with ~90k builds | 17:59:12 |
| Vladimír Čunát | So... we cancel them and ping jbedo in case there's some importance to have them "now"? | 17:59:54 |
| sterni | I guess we can ask how pressing it is? | 18:00:32 |
| sterni | in any case we are still waiting on hexa's cpython update | 18:00:43 |
| jonringer | well, if we are going to delay to get last minute PRs in. I'm fine delaying a few hours. I just started my day. But I would like to go to bed with it started | 18:01:06 |
| sterni | also is there anything in here that should be included? https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+base%3Astaging | 18:01:25 |
| hexa | In reply to @jonringer:matrix.org
so we can get some last minute things in 🙂
Sure, but this cycle is already ~3 days late
this cycle won't get into 21.11 anyway, no? | 18:08:00 |
| jonringer | incorrect | 18:08:27 |
| hexa | oops | 18:08:37 |
| jonringer | until the staging-next PR is created, staging will still be reflected | 18:08:43 |
| jonringer | * until the staging-next PR is created, staging will still be reflected in the release | 18:08:52 |
| Vladimír Čunát | It was planned to get in 21.11, with merge this Friday: https://discourse.nixos.org/t/lets-have-a-great-21-11-release-cycle/15262/3 | 18:09:31 |
| hexa | the cpython update is error-prone, due to loop kwarg deprecation warnings | 18:09:41 |
| hexa | so not a good fit for 21.11 | 18:09:51 |
| jonringer |
Unrestrict all breaking changes; new changes will not be present in master before branch-off
This is only relevant if the previous staging-next PR was able to be merged, and the new PR started on the 12th
| 18:10:36 |
| jonringer | should probably update the wording to denote the desired calendar date. Then make it clear in the schedule updates where we are | 18:17:57 |
|  nrdxp joined the room. | 19:06:18 |
 Sandro | I would suggest to make a clear diagram with dates. | 20:58:16 |
 das_j | please do | 22:39:52 |
| 16 Nov 2021 |
| Sandro | Since I am not fully understanding the current release table I don't think I am qualified for that | 10:12:57 |
| hexa | What's unclear? | 11:02:06 |
