Add Organizations release stages page

Alex Pooleyrequested to merge
ap-org-release-stages into main

What

Adds a new Release stages page for the Organizations team that defines a formal release tunnel for the Organizations surface area.

Stages: Experimental → Beta → Limited Availability → GA → Stable, each with a pre-defined audience, target platforms, and stage feature flag (organization_experimental, organization_beta, organization_la_<increment>, organization_ga).

The page also:

  • Explains how this deviates from the company-wide feature flag lifecycle (one coordinated surface vs. per-feature flags, pre-defined audiences/platforms, a retained GA handbrake, and an added Experimental stage).
  • Includes two block-beta diagrams — platform reach and audience reach — woven into the relevant sections.
  • Sources the GA/Dedicated behaviour to the GitLab Dedicated docs.

Why

Organizations is a surface area, not a single feature. Pre-defined stages give everyone (team, stakeholders, customers) a shared language for where work stands, align Engineering/Product responsibilities, reduce feature-flag friction, and give incomplete-but-large work a home (Experimental) instead of stale MRs.

Linked from

  • organizations/_index.md — new Release stages subsection under About
  • organizations/process.md — new Release stages section

🤖 Generated with Claude Code

Merge request reports