| 15 Nov 2021 |
 jonringer | https://matrix.to/#/!UNVBThoJtlIiVwiDjU:nixos.org/$INNOiUwxaKfhZhLb0DZRckaiqnJi5g82Vi83WYXp5rg?via=nixos.org&via=matrix.org&via=helsinki-systems.de | 18:42:24 |
| jonringer | cc tomberek . To remember for next release | 18:42:45 |
| 17 Nov 2021 |
|  genofire changed their profile picture. | 20:12:47 |
| 18 Nov 2021 |
 nrdxp | This was dropped in the feature freeze last minute. A little torn on how to proceed here. Any additional eyes would be great:
https://github.com/NixOS/nixpkgs/pull/146463 | 15:15:27 |
 tomberek | I'm inclined to include it. still reading... | 15:20:57 |
| jonringer | Merging it would essentially lose "two days" worth of hydra munching. I'm inclined to say merge to staging, and backport | 15:50:36 |
| tomberek | We're already a bit behind. btw: would it make sense to increase the staging-next shares to get more priority? | 16:09:12 |
| jonringer | not really, IIRC staging already has pretty high share counts with relationship of the other jobs | 16:16:35 |
| nrdxp | is there any way to wire up your megaserver as one of the builders temporarily? I don't think anyone questions your integrity here 🙂 | 16:17:25 |
| jonringer | I have questions about its integrity | 16:20:32 |
 Sandro | In reply to @jonringer:matrix.org
Merging it would essentially lose "two days" worth of hydra munching. I'm inclined to say merge to staging, and backport Just do that. It would get backported maybe a few days or a week after the release which is totally fine here | 16:28:22 |
| jonringer | In reply to @tomberek:matrix.org
We're already a bit behind. btw: would it make sense to increase the staging-next shares to get more priority? welcome to the most annoying part of doing a release, waiting for hydra to crunch builds | 16:30:06 |
| jonringer | This is why I'm particularly annoyed around the schedules slipping, it snowballs the anxiety | 16:30:59 |
| tomberek | I had a discussion with Equinix metal about interest in supporting the next release with additional hardware, devoted specifically to ZHF and staging-next builds. | 16:32:17 |
 hexa | In reply to @timdeh:matrix.org
is there any way to wire up your megaserver as one of the builders temporarily? I don't think anyone questions your integrity here 🙂 that's not going to happen out of pure principle | 19:12:24 |
| nrdxp | what principle is that? | 19:12:45 |
| hexa | the trust in hydra builders is somewhat ultimate. AFAIU they're all wiped and then netbooted into the same setup and everything happens on a trusted network. | 19:15:29 |
 @grahamc:nixos.org | Yeah we have a blank check basically and can allocate more resources as needed without much trouble | 19:24:16 |
| tomberek | This goes back to the idea of scaling up/down during ZHF/releases. | 19:27:03 |
| @grahamc:nixos.org | yep, we can do that | 19:27:32 |
| @grahamc:nixos.org | mind opening a ticket on the nixos-org-configurations repo? I can get that done in a few hours | 19:27:48 |
| @grahamc:nixos.org | in particular what types of hw which would be useful | 19:28:00 |
| @grahamc:nixos.org | (x86 vs. aarch64 I mean) | 19:28:11 |
| @grahamc:nixos.org | * (x86-linux vs. aarch64-linux I mean) | 19:28:16 |
| tomberek | at the moment it seems something else is slowing down/blocking x86_64-linux builds, not necessarily machine limitations. But i'll post something anyway, just so we get into the habit of it for future releases. | 19:35:39 |
| @grahamc:nixos.org | 👍️ it'd be good to have "open a ticket to scale up" and "open a ticket to scale down" in the RM process documentation | 19:36:21 |
| @grahamc:nixos.org | * 👍️ it'd be good to have "open a ticket to scale up" and "open a ticket to scale down" in the RM process documentation, too | 19:36:22 |
| tomberek | https://github.com/NixOS/nixos-org-configurations/issues/186 | 19:43:35 |
| tomberek | https://github.com/NixOS/release-wiki/pull/22 | 19:47:20 |
| 19 Nov 2021 |
|  sterni joined the room. | 11:04:25 |
