;doc: CHANGELOGS: update

This commit is contained in:
Simon Michael 2023-05-31 22:02:26 -10:00
parent c6afab813c
commit 5048c89608

View File

@ -10,17 +10,11 @@ Before release, and preferably daily/weekly as well:
- always first update changelogs in master branch, not in release branches - always first update changelogs in master branch, not in release branches
- `./Shake changelogs` - `./Shake changelogs`
- edit the new changelog items - edit the new changelog items
- open changelogs - open the five changelogs
- as VSC panes: - in emacs: `M-x dired-find`, `-name CHANGES.md`, `(`, split into 5 columns, open each one, narrow from last release heading to top
- explorer - in each changelog
- unfold hledger, hledger-lib, hledger-ui, hledger-web directories (?) - paste section headings from top comment if needed
- CMD-f, changesmd, click filter icon - process new items, from top-most section heading upward
- 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)
- drop boring items (changes not visible to end/API users, followups to other new items, minor doc updates..) - 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) - 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) - move to top of appropriate changelog & section (create section when needed; consider a second pane to reduce scrolling)