| 24 May 2023 |
 Robert Hensing (roberth) | For example a program that assembles release notes from individual files to avoid merge conflicts, maybe something that uses the markdown yaml header to sort by user-specified relevance levels | 15:48:14 |
| Robert Hensing (roberth) | Maybe CI configuration as well | 15:48:49 |
| Robert Hensing (roberth) | Not sure exactly what the scope should be; it's an open question. So the goal is to make releasing easier, and some of the questions are: how can we use tooling to make our lives easier? what do others do? what tooling exist or would have to be written? | 15:51:08 |
 lennart | would you be open to discuss this after the release? because then, I at least would have more insight into it and maybe good ideas for such a tool (if its is really needed) | 15:52:26 |
| Robert Hensing (roberth) | I'm asking for NixOS, but also for Nix, which releases more often https://github.com/NixOS/nix/issues/7665 | 15:52:29 |
| Robert Hensing (roberth) | of course! | 15:52:34 |
| lennart | awesome! please to write me a message, if i forget | 15:53:08 |
| lennart | * awesome! please do write me a message, if i forget | 15:53:14 |
| lennart | In reply to @roberthensing:matrix.org
I'm asking for NixOS, but also for Nix, which releases more often https://github.com/NixOS/nix/issues/7665 for now i'd go with elcos estimatian, but that probably changes | 15:54:06 |
| lennart | In reply to @roberthensing:matrix.org
I'm asking for NixOS, but also for Nix, which releases more often https://github.com/NixOS/nix/issues/7665 * for now i'd go with elcos estimation in the first comment, but that probably changes | 15:54:22 |
| lennart | * for now i'd go with Eelcos estimation in the first comment, but that probably changes | 15:54:39 |
| Robert Hensing (roberth) | yeah, this is not urgent, but we'd like to eventually automate more of the release process, and a shared tool could help both projects | 15:55:07 |
| lennart | sure! | 15:55:15 |
 raitobezarius | In reply to @roberthensing:matrix.org
Did anyone look into tooling for automating release notes? I wanted to do it | 16:09:57 |
| raitobezarius | But my priority/urgency is stabilizing the NixOS test framework | 16:10:11 |
| raitobezarius | I wanted at least to have something to generate valid empty release notes | 16:10:31 |
| raitobezarius | so that next release managers can write a file without feeling stupid :D | 16:10:39 |
| raitobezarius | I think we should also add the "test building your manual before pushing anything" step | 16:10:57 |
| raitobezarius | My plan though was something much more simpler Robert Hensing (roberth) | 16:11:32 |
| raitobezarius | Let's discuss this post-release indeed :) | 16:11:41 |
| 25 May 2023 |
| raitobezarius changed their display name from raitobezarius to disko in NixOS 23.11 when. | 13:32:55 |
| raitobezarius changed their display name from disko in NixOS 23.11 when to raitobezarius. | 13:37:47 |
| raitobezarius | FWIW, my current focus / goal is documented here: https://github.com/orgs/NixOS/projects/34/views/1 for ZHF | 17:29:53 |
| raitobezarius | squashing all NixOS tests issues (some of them I caused coughs) | 17:30:04 |
| lennart | raitobezariusand me had a good meeting today about the Release Notes editing | 17:30:50 |
| lennart | the rest is just doing | 17:31:00 |
| lennart | hexa: I'd do want your input when i'm i Darmstadt if possible | 17:31:23 |
| lennart | * hexa: I'd do want your input when i'm in Darmstadt if possible | 17:31:33 |
 hexa | sure | 17:31:57 |
| 26 May 2023 |
| raitobezarius | I don't really care about the colors of the bike but | 14:08:02 |
