From 5048c896087f83129aa33889c492a0e67c774213 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Wed, 31 May 2023 22:02:26 -1000 Subject: [PATCH] ;doc: CHANGELOGS: update --- doc/CHANGELOGS.md | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/doc/CHANGELOGS.md b/doc/CHANGELOGS.md index 3807d0069..38f987de9 100644 --- a/doc/CHANGELOGS.md +++ b/doc/CHANGELOGS.md @@ -10,17 +10,11 @@ Before release, and preferably daily/weekly as well: - always first update changelogs in master branch, not in release branches - `./Shake changelogs` - edit the new changelog items - - open changelogs - - as VSC panes: - - explorer - - unfold hledger, hledger-lib, hledger-ui, hledger-web directories (?) - - CMD-f, changesmd, click filter icon - - click project CHANGES (last one in list) - - click editor pane, split it, click rightmost editor pane - - click hledger CHANGES - - click rightmost editor pane, split it, ... etc. - - in each changelog (first ui & web; then project, cli, lib) - - process new items (starting above top-most section heading, working upward) + - open the five changelogs + - in emacs: `M-x dired-find`, `-name CHANGES.md`, `(`, split into 5 columns, open each one, narrow from last release heading to top + - in each changelog + - paste section headings from top comment if needed + - process new items, from top-most section heading upward - drop boring items (changes not visible to end/API users, followups to other new items, minor doc updates..) - drop duplicated items/content (mostly between cli and lib) - move to top of appropriate changelog & section (create section when needed; consider a second pane to reduce scrolling)