| 22 May 2024 |
 Weijia | In reply to @jonringer:matrix.org
Things I would like to see in the release notes:
- Re-introduction of the "highlights section"
- makes it easy for tech blogs and others to see major inclusions of a release
- Ensure that the affected programs/services appear at the beginning of the the release note
- See above, as an example of a note which can be restructured to have the affected packages ordered in a manner which is easier to parse
In a previous meeting, we've like the affected packages to be ordered | 13:16:34 |
| Weijia | Also, the new services section was ordered in 22.11 and 23.05, not sure why it wasn't in 23.11 | 13:17:12 |
 hexa | In reply to @jacg:matrix.org
Weijia: I see that you have sorted the entries in the release notes. I refrained from doing this because of the comment "<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. -->
" which, to be honest, I didn't really understand. Should this comment be removed, or is there some merit to it? When hundreds of people contribute to the release notes during the 6 months leading up to the release, then its's best to insert at a random location, as to avoid conflicts. This rule does not apply during release note editing, where existing entries should be sorted/grouped logically, so they're easier to digest. | 14:47:05 |
| hexa | In reply to @jacg:matrix.org
Weijia: I see that you have sorted the entries in the release notes. I refrained from doing this because of the comment "<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. -->
" which, to be honest, I didn't really understand. Should this comment be removed, or is there some merit to it? * When hundreds of people contribute to the release notes during the 6 months leading up to the release, then its's best to insert at a random location, as to avoid constant merge conflicts, because everyone appended e.g. at the end of the list. This rule does not apply during release note editing, where existing entries should be sorted/grouped logically, so they're easier to digest. | 14:47:32 |
| Weijia | I guess it might work if we replace the comment with something like "please keep the entried alphabetically sorted" for 24.11 | 14:52:57 |
| Weijia | * I guess it might work if we replace the comment with something like "please keep the entries alphabetically sorted" for 24.11 | 14:53:06 |
 Alyssa Ross | Ah, like all-packages.nix? :P | 14:59:30 |
 Mic92 | I like the approach that the nix package manager now uses with separate files. | 15:04:09 |
| Mic92 | * I like the approach that the nix package manager now uses with separate files for the changelog. Would even make more sense for nixpkgs | 15:04:22 |
 adamcstephens | for packages, maybe we could even colocate them with the package itself? | 15:05:16 |
| Mic92 | In reply to @hexa:lossy.network
vcunat: ^ @room Meeting in 55 minutes in https://jitsi.lassul.us/24.05-branch-off | 15:05:46 |
| hexa | In reply to @qyliss:fairydust.space
Ah, like all-packages.nix? :P It probably took me a year to notice that all-packages had multiple categories, that were each individually sorted alphabetically 🫠| 15:07:08 |
| hexa | I swear, that file was set up to make all of us look stupid | 15:07:28 |
| adamcstephens | it runs into similar problems as the category directories | 15:07:48 |
| hexa | yeah, so I'm kinda in love with autocalling | 15:08:07 |
| hexa | * yeah, so I'm kinda in love with autocalling and by-name | 15:08:25 |
|  NixOS Moderation Botchanged room power levels. | 15:26:10 |
| NixOS Moderation Botchanged room power levels. | 15:28:23 |
| hexa | Weijia: please give me time to merge the python reformat | 15:33:48 |
| hexa | merging python packages right now causes conflicts and prevents me from doing so 🙂 | 15:34:09 |
| hexa | https://github.com/NixOS/nixpkgs/pull/313628 | 15:34:34 |
|  a_n_d_y joined the room. | 18:17:14 |
 Arian | stableBranch = false doesn't look correct to me? https://hydra.nixos.org/jobset/nixos/release-24.05#tabs-configuration | 21:05:32 |
| Arian | Or do we only change that once it's 31 may? | 21:05:51 |
 Lily Foster | two days before. check wiki: https://nixos.github.io/release-wiki/Final-Release.html | 21:06:43 |
| Arian | thanks! :D | 21:08:00 |
 raitobezarius | https://github.com/nix-community/nix-index/releases/tag/v0.1.8 hexa | 21:15:15 |
| hexa | ship it | 21:15:30 |
| hexa | we updated nixos-channel scripts to the commit fwiw | 21:15:37 |
| raitobezarius | i hope i didn't fuck up | 21:15:41 |
