| 21 Apr 2024 |
 jonringer |
the .csv format used to define lua packages to be updated via
luarocks-packages-updater has changed: src (URL towards a git repository) has now become rockspec (URL towards a rockspec) to remove ambiguity regarding which rockspec to use and simplify implementation.
| 18:35:10 |
| jonringer | 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
| 18:42:07 |
 @jacg:matrix.org | Any guidelines on how granular we want the commits and PRs to be? | 21:37:24 |
| @jacg:matrix.org | Should we change package names to inline code blocks (backticks) and match the package's pkgs attribute name? For example, should things like 'YouTrack is bumped to 2023.3. become 'youtrack is bumped to 2023.3.' ? | 21:42:08 |
| @jacg:matrix.org | * Should we change package names to inline code blocks (backticks) and match the package's pkgs attribute name? For example, should things like 'YouTrack is bumped to 2023.3.' become youtrack is bumped to 2023.3.' ? | 21:42:29 |
| @jacg:matrix.org | * Should we change package names to inline code blocks (backticks) and match the package's pkgs attribute name? For example, should things like "YouTrack is bumped to 2023.3." become "youtrack is bumped to 2023.3." ? | 21:42:54 |
| @jacg:matrix.org | Concerning 'Ensure that the affected programs/services appear at the beginning of the release note" are we happy with "The mpich package expression now requires ..." or should this become something like "mpich: the package expression now requires ..." ? | 21:46:26 |
| @jacg:matrix.org | * Concerning "Ensure that the affected programs/services appear at the beginning of the release note" are we happy with "The mpich package expression now requires ..." or should this become something like "mpich: the package expression now requires ..." ? | 21:50:11 |
