| 2 Apr 2023 |
 nixinator | * K3s and associated ‘server orchestrated’ probably needs to be split out to flakes .man not be in nixpkgs at all. This the flake maintainers can decide all the EOL stuff . | 06:13:46 |
| nixinator | * K3s and associated ‘server orchestrated’ probably needs to be split out to flakes .and not be in nixpkgs at all. This the flake maintainers can decide all the EOL stuff . | 06:14:31 |
| nixinator | * K3s and associated ‘server orchestrated’ probably needs to be split out to flakes .and not be in nixpkgs at all. The flake maintainers can decide all the EOL stuff . | 06:14:44 |
 riotbib | Redacted or Malformed Event | 06:19:38 |
 hexa | In reply to @nixinator:nixos.dev
K3s and associated ‘server orchestrated’ probably needs to be split out to flakes .and not be in nixpkgs at all. The flake maintainers can decide all the EOL stuff . I think the outlined plan can work. | 09:40:23 |
| 3 Apr 2023 |
 raitobezarius | https://github.com/NixOS/nixpkgs/issues/224457 | 10:22:58 |
| raitobezarius | riotbib: we should probably mention this new DE (Budgie Desktop): https://github.com/NixOS/nixpkgs/issues/224457#issuecomment-1494084278 in the release notes if it has not been done already | 10:41:29 |
| raitobezarius | hexa: gathering from the answer of Cinnamon maintainers on mozjs, it seems like https://github.com/NixOS/nixpkgs/issues/157874 won't be closed for 23.05, right? | 10:44:11 |
 Vladimír Čunát | In reply to @raitobezarius:matrix.org
https://github.com/NixOS/nixpkgs/issues/224457 Looks like you reached a ping limit by the end of the issue's original post? (the names aren't linkified) | 10:56:22 |
| raitobezarius | thank you Vladimír Čunát | 10:58:10 |
| raitobezarius | I will drive the efforts for removal of some LLVM versions, FWIW | 11:07:55 |
| riotbib | In reply to @raitobezarius:matrix.org
riotbib: we should probably mention this new DE (Budgie Desktop): https://github.com/NixOS/nixpkgs/issues/224457#issuecomment-1494084278 in the release notes if it has not been done already already added, thanks for the hint! https://github.com/NixOS/nixpkgs/blob/master/nixos/doc/manual/release-notes/rl-2305.section.md?plain=1#L50 | 11:19:29 |
| raitobezarius | we should put it with more emphasis | 11:19:52 |
| raitobezarius | as it is a complete DE | 11:19:55 |
| riotbib | ah got it | 11:21:58 |
| riotbib | its on my TODO now | 11:22:02 |
| riotbib | raitobezarius and me are considering hotlinking screenshots to new software like Budgie Desktop in the Release Notes. does someone have an idea where to host it - just in case we do it? | 11:28:06 |
| riotbib | in the repo doesn't seam to ideal :D | 11:28:20 |
| * riotbib will also bring up this question in the PR that puts more emphasis on Budgie Desktop | 11:29:14 |
| raitobezarius | re: improving the RM process | 12:01:56 |
| raitobezarius | I feel like things like https://github.com/NixOS/nixpkgs/issues/40015 should be part of the release process | 12:02:02 |
| raitobezarius | like a "let's upgrade everything round up" | 12:02:07 |
 Janne Heß | Sounds like a good idea | 12:11:45 |
| raitobezarius | Also, I feel like some leftover issues in 23.05 milestone that get moved to next release can only be fixed by a focus group during some days (hackathon/whatever), such as this https://github.com/NixOS/nixpkgs/issues/49528
I think having a list of "hackathon"-level issues can help coordinate sprints on those. (cc hexa you mentioned the same for PAM subsystem IIRC)
| 12:16:13 |
| Janne Heß | In reply to @raitobezarius:matrix.org
Also, I feel like some leftover issues in 23.05 milestone that get moved to next release can only be fixed by a focus group during some days (hackathon/whatever), such as this https://github.com/NixOS/nixpkgs/issues/49528
I think having a list of "hackathon"-level issues can help coordinate sprints on those. (cc hexa you mentioned the same for PAM subsystem IIRC)
Documentation should be improved by now: https://nixos.org/manual/nixos/stable/index.html#sec-switching-systems | 12:18:03 |
| Janne Heß | This is however still very technical | 12:18:08 |
| raitobezarius | And I feel like the whole thing should be redesigned to avoid annoying bugs | 12:18:29 |
| raitobezarius | This would probably be helpful towards fail-safe auto-rollbacks (which is also an open issue somewhere) | 12:18:43 |
 Linux Hackerman | In reply to @vcunat:matrix.org
Looks like you reached a ping limit by the end of the issue's original post? (the names aren't linkified) Maybe it should be a PR which he rebases wrong instead 😏 | 12:19:45 |
| raitobezarius | new weird trick to ping everyone dropped | 12:19:59 |
