| 30 Jun 2022 |
 hexa | The last release I went through all open release-branch PRs and closed them with a template message. | 15:59:41 |
| hexa | https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+base%3Arelease-21.11 | 16:36:15 |
 Vladimír Čunát | You can choose various options when protecting a branch, but I can't see a complete freeze. Maybe it could be hacked from some of the options like "Require deployments to succeed before merging" but I certainly don't feel motivated to work on it. | 18:09:40 |
| 1 Jul 2022 |
 Janne Heß | In reply to @hexa:lossy.network
doesn't mean you can't PR into it, no? ah well | 21:01:48 |
| hexa | took care of closing all remaining PRs | 21:57:00 |
| 2 Jul 2022 |
|  Amit Levy left the room. | 08:28:16 |
| 4 Jul 2022 |
| Janne Heß | In case anyone is interested in reviewing: https://github.com/NixOS/release-wiki/pull/44 | 18:10:08 |
 jonringer | lgtm | 18:25:10 |
| Janne Heß | noice | 18:25:18 |
| Janne Heß | would have been horrible if there were huge mistakes because I already did all that :D | 18:25:32 |
| 8 Jul 2022 |
| Janne Heß | I kind of forgot myself, but it looks like the retrospective is in 15min 👀 does anyone plan on coming? | 16:45:45 |
| hexa | I can join, but I don't have much to add 😲 | 16:53:31 |
| Janne Heß | In reply to @hexa:lossy.network
I can join, but I don't have much to add 😲 Same | 16:53:58 |
| hexa | we can remain silent for 5 minutes, tell everyone it was a productive meeting and move on | 16:54:26 |
| hexa | do you have a link? | 16:55:04 |
| Janne Heß | I'll be home in 2min | 16:56:00 |
| hexa | doesn't make sense to start without you! | 16:56:31 |
| Janne Heß | https://meet.jit.si/nixos-22.05-release-retrospective | 16:59:45 |
|  biohazard6743 joined the room. | 18:05:31 |
| hexa | errata: schedule the retrospective earlier than 1 month after everything important happened | 23:21:29 |
| 10 Jul 2022 |
| Janne Heß | In reply to @hexa:lossy.network
errata: schedule the retrospective earlier than 1 month after everything important happened Something to add: there needs to be a working way of communicating with the infrastructure team as they need to do tasks that a RM cannot do | 13:36:56 |
| 26 Jul 2022 |
|  underpantsgnome changed their display name from tinybronca to tailrec. | 14:42:13 |
| underpantsgnome changed their display name from tailrec to tinybronca. | 15:43:17 |
| 30 Jul 2022 |
|  Sandro 🐧 changed their display name from Sandro to Sandro 🐧. | 13:16:59 |
| 1 Aug 2022 |
|  better_sleeping joined the room. | 09:08:09 |
| better_sleeping left the room. | 09:08:37 |
| 16 Aug 2022 |
 trofi | Silly question: when do we update bootstrap-files? (like https://github.com/NixOS/nixpkgs/blob/master/pkgs/stdenv/linux/bootstrap-files/x86_64.nix). Maybe we should do it every release at least for hydra-supported systems?
Every time I discover that our current gcc gets built by gcc-8 (2019), glibc-2.27 (2018) and binutils-2.32 (2019) I shudder to think how many bugs we have there and think twice if I should report something upstream or spend time to update those locally to double-check it's not just outdated versions.
| 09:15:14 |
| Vladimír Čunát | Doesn't the gcc build system actually build twice inside? (To get built itself by itself.) | 10:55:00 |
| trofi | Yeah, gcc bootstraps (from gcc-8.3.0). But things like GNU make are still old ones: https://dpaste.com/A99VZ9J88.txt. I added a silly mode to make recently and was surprised I could not use it for gcc attribute itself. | 12:04:20 |
| 17 Aug 2022 |
|  greaka joined the room. | 20:21:30 |
