CAMARA Release Naming
Summary
History can be found here
TSC has voted for H1/xxxx and H2/xxxx
Outreach Committee is asked to check / propose more marketing-friendy names
Brainstorming / proposals from the team:
tbd
tbd
“Signal” / “Sync”
Telecom Native Terms
“Signal” Initiates and “Sync” aligns
Geographically friendly
Ex: Signal26, Sync26, Signal27, Sync27
Comments
Dec 18, 2025
Jan 19
“Signal” / “Sync”
Telecom Native
“Signal” Initiates and “Sync” aligns
Geographically friendly
Ex: Signal26, Sync26, Signal27, Sync27
Markus Kümmerle
(edited)
Let me summarize the criteria for the CAMARA meta-release naming from the discussion in #200:
Semantically meaningful — convey the distinct purpose of each release:
H1: introduces updated Commonalities/ICM and innovative/sandbox APIs (sets direction)
H2: updates APIs to new Commonalities, consolidates work (ensures interoperability and stability)
Globally neutral — no geographic or seasonal bias (hemisphere-neutral)
Memorable and human-friendly — usable by Release Management on a daily basis, not sterile technical identifiers
Professional for external communication — suitable for marketing, documentation, and presentations
Technically usable in automation, YAML files, and repository names:
Single token (no spaces or punctuation if possible)
Directly attachable to year (e.g., Spark26, 2026H1)
No special characters, accents, or typography that invite variants
Understandable for non-native English speakers — CAMARA is an international community
Low connotation risk — avoid terms that could suggest fraud, defects, or have unintended negative meanings in other contexts
Minimal trademark/branding conflicts — avoid overlap with well-known products or projects (e.g., Apache Spark, Amazon Prime, 3GPP Forge)
BTW fulfills Spring/Fall also not really the first criteria, after the two meta-releases are no longer equal.
We might need to think about a migration period where we introduce new names together with Spring26 and Fall26.