release 1.4.1: generic docs and canonical install path
Docs use generic ops/outside-runner wording; install path ~/src/taler-monitoring. VERSION 1.4.1 patch on top of the 1.4.0 scheme release.
This commit is contained in:
parent
0f31fa76a5
commit
52684fd64f
16 changed files with 77 additions and 52 deletions
|
|
@ -15,7 +15,7 @@ How we commit, tag, and push this **standalone** suite
|
|||
| Clone | `~/src/taler-monitoring` |
|
||||
| Remote | `https://git.hacktivism.ch/hernani/taler-monitoring.git` |
|
||||
| Branch | `main` |
|
||||
| Tags | `vX.Y` / `vX.Y.Z` (see [`VERSIONS.md`](./VERSIONS.md)) |
|
||||
| Tags | `vMAJOR.FEATURE.FIX` (see [`VERSIONS.md`](./VERSIONS.md)) |
|
||||
| Symlink (optional) | `~/taler-monitoring` → suite dir (`update-suite.sh`) |
|
||||
|
||||
There is **no** `scripts/` subtree under an ops admin-log for this suite.
|
||||
|
|
@ -30,7 +30,7 @@ Host ops (Caddy, landings, day logs) stay in **koopa-admin-log** (separate repo)
|
|||
| **Commits** | Prefer frequent small commits (`area: short description`) |
|
||||
| **Areas** | e.g. `host-agent: …`, `site-gen: …`, `monpages: …`, `docs: …`, `release: …` |
|
||||
| **Push** | At end of a work slice / session — not after every micro-commit |
|
||||
| **Tags** | After a fix/feature lands on `main`, tag + push tag (e.g. `v1.3.3`) |
|
||||
| **Tags** | After a fix/feature lands on `main`, tag + push tag (e.g. `v1.4.1`) |
|
||||
|
||||
```bash
|
||||
cd ~/src/taler-monitoring
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue