Release Scheme

Release scheme

Both repositories (OpenIMP and open-tx-isp) use the same scheme. Not to be confused with thingino-firmware's own branch aperto, which pins the revisions described here.

Ref	Purpose
main	the original author's line; left untouched, a strict ancestor of aperto
aperto	the released open stack (OpenIMP + open-tx-isp); fast-forward only; every commit was flashed and checked on cameras
tags vYYYY.MM.DD	date tags on aperto, so thingino can pin a tag instead of a SHA on a moving branch

Development and the device-test campaign run in the Lu-Fi forks (integration branch next, topic branches claude/<topic>); tested work reaches aperto after a clean soak.

For packagers

• Pin OPENIMP_VERSION and OPEN_TX_ISP_VERSION in the thingino package files (package/openimp/openimp.mk, package/open-tx-isp/open-tx-isp.mk) to a tag (or a full commit SHA on aperto).
• Always pin both packages to matching revisions of the same release: the driver and the library share ABI details (control IDs, ioctl layouts, rmem handling).
• Flash complete OTA images when changing either revision.

Aggregates

During the test campaign, tested combinations were named "all-N". An aggregate is a set of branches merged into one commit per repository, flashed on the test cameras and soak-tested before it was released.