Precis of the current MergeTB release mental model
YMMV this is incomplete and a work in progress, and I will update it in place. Please feel free to comment with additional information that I can roll into this.
Overview
The current MergeTB release model uses a single APT repository using the Debian-style “first component is the release code-name” convention:
deb https://pkg.mergetb.net/debian bullseye main
Snap packages are also used, but the mid-to-long term intent is to transition completely to deb packages as the common denominator.
Targeted distributions
Currently Debian bullseye is the preferred baseline for installation of most Merge software, with buster supported as well.
Workflow/lifecycle
details forthcoming, still doing the homework
Reference Material
GitLab repositories