Define naming convention and colors for meta-release labels

[hdamker]

Problem description

Meta-release labels across camaraproject repositories use inconsistent naming and colors. An inventory (Feb 2026) found:

• Fall25 exists in 6 naming variants: Fall25 (29 repos), fall25 (6), Fall 25 (5), Fall'25 (2), Fall25 M3 review (1), Fall25 M4 review (1)
• Spring25 uses 15 different colors across 15 repos
• Fall25 uses 21 different colors across 29 repos
• Similar inconsistencies for Spring26, Fall24

This makes organization-wide queries by label unreliable and causes confusion when moving between repositories.

Possible evolution

Define a standard convention for meta-release labels:

1. Naming: Fall26, Spring27, etc. — capitalized season, two-digit year, no spaces or apostrophes
2. Color: One consistent color per cycle across all repos (e.g., a fixed color for Fall cycles, another for Spring)
3. Rollout: Create Fall26 with agreed name and color across all active API repositories via script

Past meta-release labels (up to Fall25 / Spring26) can remain as-is — the cost of renaming exceeds the benefit.

Additional context

Part of the broader label standardization effort: camaraproject/project-administration#120