[Important] Cobalt 24 Stable Versions are now multiples of 10
Lam Bui
TL;DR; For YouTube Certification and Cobalt Device Maintenance Updates, use only Cobalt 24 Stable Releases, which are identified with the minor version being a multiple of 10.
✅ [STABLE] e.g. 24.lts.10, 24.lts.20, 24.lts.30, … , 24.lts.60
❌ [non-STABLE] e.g. 24.lts.1 (RC1), 24.lts.2 (RC2), 24.lts.14 (non-Stable), 24.lts.26 (non-Stable)
Starting with Cobalt 24, the version numbering scheme for LTS Major and Minor Stable releases are now numbered by multiples of 10. This change aligns with semantic versioning, adds more sensible differentiation for Stable vs incremental non-Stable releases, and enables the Cobalt team to deliver faster fixes, optimizations, and features to our mutual users. Please only use Cobalt LTS releases with minor versions that are multiples of 10 for YouTube Certification and Cobalt Device Maintenance Updates.
NOTE: Pre-built Evergreen binaries are only available for Stable (non-RC) releases at this time.
For example:
FAQs
What is the reasoning behind the versioning change?
The Cobalt team is focused on being able to deliver faster fixes, optimizations, and features to our mutual users. Being able to iterate quickly while testing and validating smaller sets of changes between releases increases velocity of the team to be able to support partners and our products.
What version should I use for certification?
Only Stable Cobalt versions. This is the same policy as before with the Cobalt 24 numbering scheme as the only change.
E.g. Cobalt 24.lts.10, 24.lts.20, 24.lts.30,...., 24.lts.50
What about Evergreen binary versions?
Stable Evergreen binaries will also be numbered similarly with minor version numbers
E.g. 24.lts.10 (Evergreen binary version 4.10.0)
NOTE: non-Stable pre-built Evergreen binaries will not be available on GitHub yet, but the Cobalt Team is planning on having complimentary pre-built non-Stable Evergreen binary releases in the future for incremental early testing.
Will Evergreen binaries be provided for all Cobalt releases?
No, at this time, pre-built Evergreen binaries will only be available for Stable releases (e.g. 24.lts.10, 24.lts.20, …, 24.lts.60). In the future, the Cobalt Team is planning to release matching pre-built Evergreen binaries for RC (non-Stable) releases that will be announced at a later time.
If you would like to do your own testing on RC releases, please build the Cobalt Evergreen binaries for your respective platform (e.g. evergreen-arm-softfp) locally.
 | • Lam Bui |
