Which version to use?
Current versions
LTS: 2.1
Latest: 2.2
LTS Candidate: 2.2
Version numbers follow Semantic Versioning: minor releases add features (2.x.0), patch releases contain bug fixes only (2.x.y).
The three tiers
LTS (Long Time Support)
Choose LTS for the lowest operational risk.
LTS is the recommended track for production projects that prioritize stability over new functionality.
What to expect
- Conservative change rate
- Patch updates are bug fixes only
- Longer support window (security and high-impact fixes are backported)
Typical users
- Large deployments
- Existing projects that don't need new features
Latest (latest feature release)
Choose Latest when you need the newest features and/or best performance.
Latest is the most recent feature-bearing minor line. It is intended for projects that require new capabilities on a shorter timeline.
What to expect
- Version with the newest features and best performance
- Patch updates remain bug fixes only
Typical users
- New projects
- Feature-driven projects
LTS Candidate
LTS Candidate is the version that is expected to become the next LTS. As soon as it has proven real-world stability across diverse environments it will be promoted to the new LTS.
What to expect
- No new features (fixes only)
- May be promoted to LTS after sufficient soak time (real-world proven stability)
- Golden mean between LTS and Latest: Relatively new, but has received all fixes
Typical users
- Pilot customers/sites
- Projects that need the new features in this version, but don't need any upcoming features.
It is possible multiple tiers are on the same version. For example if the latest version is picked as the LTS Candidate, Latest and LTS Candidate point to the same version.
How promotion works (LTS Candidate → LTS)
The Capture team will pick a minor version as LTS Candidate. After sufficient field soak time (field experience) and possibly fixes, the same minor line is promoted to LTS.
How to update
Use the same rollout discipline whether you are on LTS, Latest, or LTS Candidate.
- Install and verify in a staging/test environment
- Validate: Check if the data you expect is correctly collected and synced.
- Deploy and verify on a single device: Choose a representative gateway. Monitor logs, performance, and data continuity.
- Scale up: Roll out gradually (small batch → larger batch) until the full fleet is updated.
Avoid “big bang” updates across the entire fleet without staged verification.