| 14 Oct 2023 |
| @lorenzleutgeb:matrix.org joined the room. | 13:41:22 |
| 15 Oct 2023 |
| kazimk joined the room. | 17:35:52 |
| 16 Oct 2023 |
figsoda | https://github.com/NixOS/nixos-artwork/issues/104 | 16:45:58 |
lennart | Awesome will draft something the following days | 16:48:11 |
| 18 Oct 2023 |
| ghishadow changed their profile picture. | 12:51:59 |
| 19 Oct 2023 |
lennart | following up on that: https://github.com/NixOS/nixos-artwork/pull/105 | 15:40:47 |
| 20 Oct 2023 |
@alejandrosame:matrix.org | Hi all!
I've been working the last couple of days on a release notes generator after having merge conflicts and receiving feedback from contributors that wanted to have the file be split.
You can check the draft PR (https://github.com/NixOS/nixpkgs/pull/262296) and start giving feedback since I won't be refactoring the script and structure further.
I talked already with raitobezarius about this change and he also pointed me to ask here which approach would you like to take to move forward with the autogeneration of the release notes. The idea is that the we limit changes to the collected release notes file made by contributors. Some of the options are:
- Having a bot autocommiting the release notes to the repo, so it is still rendered by github.
- Limiting commiting to the main release notes file to only release managers and editors. The could from time to time generate the file and commit it to the relevant location.
- Having a manual build output so people can check the rendered version locally. This would have to be done either way as part of the build task for the manual.
Please, share your ideas and comments :)
| 13:58:32 |
| 21 Oct 2023 |
| nki ⚡️ left the room. | 23:01:50 |
| 23 Oct 2023 |
lennart | wow this is super cool alejandrosame, I am a bit busy this week (due to having a night shift this week at work), but would give feedback the week after | 06:16:27 |
| globin joined the room. | 09:50:49 |
| globin set a profile picture. | 14:27:46 |
| 25 Oct 2023 |
| @federicodschonborn:matrix.org changed their profile picture. | 00:12:34 |
| fgaz joined the room. | 07:40:17 |
| 27 Oct 2023 |
| @federicodschonborn:matrix.org changed their profile picture. | 01:24:12 |
| 29 Oct 2023 |
raitobezarius | https://github.com/NixOS/nixpkgs/pull/259884 | 11:54:23 |
raitobezarius | merged | 11:54:24 |
| 30 Oct 2023 |
raitobezarius | https://github.com/NixOS/nixpkgs/pull/264358 | 13:56:00 |
raitobezarius | dropping nodejs stuff | 13:56:03 |
raitobezarius | I'm doing the ruby 3.0 drop PR too | 14:02:07 |
raitobezarius | and I will drop probably some old LLVM stuff we can afford to drop | 14:02:16 |
raitobezarius | we don't have good solutions when the manual break because of removed services… | 14:09:19 |
raitobezarius | do we? | 14:09:22 |
raitobezarius | https://github.com/NixOS/nixpkgs/pull/264361 | 14:13:11 |
Vladimír Čunát | Old clang is easier to drop than old gcc? IIRC we didn't get far there. | 14:14:03 |
Vladimír Čunát | (and ended up keeping may gcc versions, after some discussions) | 14:14:27 |
Vladimír Čunát | * (and ended up keeping many gcc versions, after some discussions) | 14:14:33 |
hexa | also weird to start this process today | 14:17:46 |
hexa | * also weird to start remving old compilers today | 14:18:08 |
raitobezarius | https://github.com/NixOS/nixpkgs/pull/264364 | 14:19:48 |
raitobezarius | In reply to @vcunat:matrix.org Old clang is easier to drop than old gcc? IIRC we didn't get far there. We can indeed drop 5 & 6 | 14:19:54 |