;doc: RELEASING: updates
This commit is contained in:
parent
10a36e64a7
commit
708d55c2dd
@ -108,14 +108,14 @@ These have complex interdependencies and sequencing constraints. Chunk, separate
|
||||
- Before tagging: make binaries for all platforms, from the same commit.
|
||||
- Before making binaries: do all possible pre-tagging steps and try to get everything finalised. (Binaries' --version shows their git hash, and this should match the release tag.)
|
||||
|
||||
## Value map
|
||||
## Releasing diagram
|
||||
|
||||
Here is a map of the value chain and artifacts involved in a hledger major release.
|
||||
From this we derive the procedures below, and ideally more automated tools over time.
|
||||
Here is a map of the value chain, artifacts, tasks and levels of release readiness involved in a hledger release. Arrows indicate dependencies. When making a release, activity moves from the bottom up towards the top. From this we derive the procedure docs below, and gradually automate those more over time.
|
||||
|
||||
[](HledgerReleaseValueMap.png)
|
||||
|
||||
## Procedures
|
||||
These docs need update.
|
||||
|
||||
### Release
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user