| 26 Apr 2024 |
 Mic92 | * Alright. I didn't check that. I was just seeing a message in the 23.04 release issue regarding python bumps | 15:03:40 |
 Sandro | In reply to @joerg:thalheim.io
I think the trick with that is to already start ahead of time with refactoring the release notes and not wait till the end. But it's hard to write a coherent text while other people do random edits in between. maybe first do line by line edits and then resort it? At least not everything at once | 15:06:27 |
| Sandro | Also trimming the lines to 80 char line length helped a lot at making the diff hard to review and read | 15:06:45 |
| Mic92 | The 80 line length limit made it harder or easier to review? | 15:11:25 |
 figsoda | Unfortunate timing for me to nominate jonringer right before he got banned 😥
Yeah I think Mic92 would be a great fit for the position
| 15:13:08 |
| figsoda | * Unfortunate timing for me to nominate jonringer right before he got banned 😥
Yeah I think Mic92 would be a great fit for the position if there wasn't a consensus already
| 15:13:21 |
| Mic92 | I think now there is. | 15:13:59 |
| Mic92 | Why do we even have the Marketing team in this checklist? https://github.com/NixOS/nixpkgs/issues/303286 | 15:28:32 |
| Sandro | In reply to @joerg:thalheim.io
The 80 line length limit made it harder or easier to review? Way harder as that was also included in the big commit and git couldn't detect any moved lines anymore and it kinda turned it to a big hunk | 15:30:19 |
 raitobezarius | In reply to @joerg:thalheim.io
Why do we even have the Marketing team in this checklist? https://github.com/NixOS/nixpkgs/issues/303286 Communication wise I suppose | 15:30:56 |
 hexa | In reply to @joerg:thalheim.io
Why do we even have the Marketing team in this checklist? https://github.com/NixOS/nixpkgs/issues/303286 The list is autogenerated | 15:31:02 |
| Mic92 | Ok. I will than just check that one and documentation. | 15:31:29 |
| Mic92 | hexa: we use mile stones for release critical issues/prs, right? | 15:36:10 |
| hexa | Projects | 15:36:23 |
| hexa | On the org | 15:36:31 |
| hexa | They have kanban boards, which is neat | 15:36:48 |
| Mic92 | Ok. I pinged members from all teams except ocaml and coq. | 15:43:10 |
 @jacg:matrix.org | In reply to @sandro:supersandro.de
random release editor note I remember from last year: please do proper git commits and not just one giant commit that reranges and reformats everything. Thanks I've been chipping away with smallish commits and PRs. | 16:34:46 |
| @jacg:matrix.org | However, I've been working against master. Should I have been doing it on staging? | 16:35:12 |
| @jacg:matrix.org | Heads-up / reminder : I'll be offline most of the upcoming weekend. | 16:35:52 |
 infinisil | In reply to @jacg:matrix.org
However, I've been working against master. Should I have been doing it on staging? Master sounds right for now. It gets trickier once the branch-off happens :P | 17:16:11 |
| infinisil | The problem last year was that the release notes were rearranged completely, but they were missing some release notes from backported PRs | 17:17:23 |
| infinisil | Something like that lead to a messy merge | 17:17:32 |
| infinisil | So my suggestion to resolve that: Rearrange the release notes as early as possible, such that they just need minor polish towards the release date | 17:18:26 |
| infinisil | Oh and I'll write the release notes for lib, I guess I should get to that soonish | 17:19:00 |
|  @patka_123:matrix.org left the room. | 19:34:10 |
| 27 Apr 2024 |
| Mic92 | Weijia: I think you have the super powers to invite new folks into this team? https://github.com/orgs/NixOS/teams/nixos-release-managers | 07:28:04 |
 Weijia | Yes | 07:29:34 |
| Mic92 | According to the release wiki we are also supposed to remove older release maintainer | 07:32:18 |
|  @maxeaubrey:matrix.org left the room. | 10:16:20 |
