Skip to content

Release Scheme

Lu-Fi edited this page Oct 11, 2026 · 3 revisions

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 (opensensor) or the fork's default branch (Lu-Fi); not the tested stack
next integration branch in the Lu-Fi forks: tracks the tested aggregate; fast-forward only
aperto the released open stack in the opensensor repositories: fast-forward only from next after a clean soak; every commit was flashed and checked on cameras
tags vYYYY.MM.DD (and -rcN) date tags, so thingino can pin a tag instead of a SHA on a moving branch

Current state: RC1

The first tag is the release candidate v2026.10.11-rc1 (2026-10-11), set on both repositories:

Repository Tag points at Branch
OpenIMP fe9307c (agg-35 687a68e4 + RC1 documentation) next (Lu-Fi) and aperto (opensensor) are at the tag
open-tx-isp 191be6c5 (driver 6e464ac7 + RC1 documentation) next (Lu-Fi) and aperto (opensensor) are at the tag

Release pages: openimp, open-tx-isp. Supported SoCs: release T10, T20, T21, T23, T31; experimental T30, T40, T41. After RC1 the next work (agg-36: T40 rate control and H.265, further vendor-API gaps, T41 mask/zoom) goes through next and reaches aperto after its own soak.

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 the 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" and later "agg-N" (RC1 is agg-35). 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.

Clone this wiki locally