Phase 20: package Linux builds and document release and maintenance workflows
This commit is contained in:
parent
6b85f28add
commit
830b6e1914
22 changed files with 490 additions and 17 deletions
|
|
@ -54,3 +54,21 @@ semantics. Physical devices, power loss, sustained recording/performance, user
|
|||
acceptance on other distributions and binary redistribution are still separate
|
||||
qualification work. There is no DEB/RPM/AppImage, bundled runtime, autosave,
|
||||
external plugin host or stable shared-library extension ABI in this release.
|
||||
|
||||
## Phase 20 local binary packaging and installed workflow
|
||||
|
||||
`make test-package` builds the release, stages installation only in a temporary
|
||||
DESTDIR, writes a normalized Linux binary/development archive, checks its SHA-256
|
||||
sidecar and per-file manifest, relocatable pkg-config paths and headless commands.
|
||||
Same-host repeated packaging is byte-identical; dependency versions and toolchain
|
||||
still determine binary compatibility. `make test-install` now repeats installation
|
||||
to verify repair/upgrade of owned files while preserving an unrelated sentinel,
|
||||
then compiles both C99 and C++17 installed consumers that create MIDI, save/reopen
|
||||
and compare nonzero exact rendering. Removal remains exact and idempotent.
|
||||
|
||||
USER_MANUAL.md consolidates operation; KNOWN_LIMITATIONS.md lists qualification
|
||||
gaps; MAINTENANCE.md defines the release checklist, regression and compatibility
|
||||
policy. Build diagnostics make no server/plugin calls. There is no asynchronous
|
||||
crash uploader or signal-handler cleanup: inspect OS core/debugger evidence on
|
||||
the control side, preserving project/media recovery paths. No release is publicly
|
||||
published by these commands, and human/device/listening checks remain pending.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue