-
Notifications
You must be signed in to change notification settings - Fork 47
Description
Context
CAMARA currently uses Spring and Fall as labels for its two meta-releases each year. While this was clear in the early stages, these terms create challenges in a global project:
- Seasons are not universal (e.g., hemispheres, equatorial regions).
- The terminology feels region-specific and not inclusive for our international community.
Need
We should agree on new names that are:
- Globally neutral (no geographic/seasonal bias)
- Meaningful in the CAMARA context
- Expressive of the distinct purpose of each release cycle
- Technically usable in YAML files, repository names, and automation — ideally:
- single token (no spaces or punctuation),
- directly attachable to year (e.g.
Spark26,2026H1), - consistent and low risk of drift (no special characters, accents, or typography that invite variants).
See also the [Meta-Release Concept discussion](#194).
Opportunity
The updated release cadence concept defines:
- First half-year release (currently “Spring”) → introduces updated Commonalities and innovative / sandbox APIs. This release sets direction for the year.
- Second half-year release (currently “Fall”) → updates APIs to the new Commonalities and consolidates the work. This release ensures interoperability and stability across the ecosystem.
This creates the opportunity to adopt names that better reflect this innovation → stability lifecycle.
Initial alternatives for discussion
(these examples are only meant to open the conversation — the community may propose entirely different directions)
Metaphoric pairs (innovation → stability)
-
Cast26 / Forge26
- Cast = initial mold, Forge = hardened and stable.
- ✅ Elegant lifecycle metaphor.
- ⚠ Risks: “cast” (broken bone), “forge” (forgery), overlap with 3GPP Forge.
-
Rise26 / Forge26
- Rise = growth, momentum; Forge = consolidation.
- ✅ Positive tone, fits lifecycle.
- ⚠ Still inherits “forge/forgery” risk.
-
Spark26 / Anchor26
- Spark = burst of energy, innovation; Anchor = stability, grounding.
- ✅ Clear lifecycle, globally understandable, YAML-safe.
- ⚠ “Spark” overlaps with Apache Spark but less problematic than “Ignite.”
-
Frame26 / Build26
- Frame = initial outline; Build = complete and strengthen.
- ✅ Pragmatic, engineering-oriented, neutral in meaning.
- ⚠ Less inspiring, but very usable technically.
-
Prime26 / Set26
- Prime = first, leading, decisive; Set = complete set of APIs aligned with Commonalities.
- ✅ Fits CAMARA cadence well: Prime = innovation + direction, Set = full alignment.
- ⚠ “Prime” has some branding overlap (Amazon Prime), but context is different.
Descriptive options
-
Foundation26 / Consolidation26
- Foundation = updated Commonalities and new APIs; Consolidation = alignment and integration.
- ✅ Clear, low risk, YAML-safe.
- ⚠ Less distinctive, more corporate tone.
-
2026H1 / 2026H2
- Simple half-year identifiers.
- ✅ Unambiguous, globally neutral, safe in automation.
- ⚠ Very plain — may feel uninspiring.
Next steps
- Gather community feedback on the naming direction (metaphoric vs descriptive).
- Test candidate names with non-native English speakers.
- Consider long-term clarity and trust (e.g., avoid terms that could suggest fraud or defects).
- Decide on a new pair before the next release cycle, so we can start using it consistently in docs, slides, and repositories.
👉 Question to the community:
What naming direction do you feel best represents CAMARA’s global character and the dual nature of our releases — a metaphoric pair (e.g. Spark26/Anchor26 or Prime26/Set26) or a descriptive scheme (e.g. Foundation26/Consolidation26 or 2026H1/2026H2)?