What GitHub’s public roadmap teaches about release phases

An independent study of exploratory, preview, and general-availability labels in GitHub’s public roadmap, with an original editable Open Source Release Board.

Independent Roadmapi study; not affiliated with GitHub. Original source.

The useful pattern

An item’s phase can answer a different question from its expected quarter: how ready is it, and what feedback is useful?

What we observed

• GitHub’s roadmap guide uses labels such as exploring, in design, public preview, and general availability to describe release maturity.
• Its project board communicates a broad shipping horizon, while exploratory items can appear without a timeframe. The repository includes a forward-looking disclaimer.

Adapt it for your roadmap

• Separate exploratory work from committed releases. Pair phase labels with a plain-language definition and a visible feedback route.
• The Open Source Release Board uses fictional initiatives, issue-like cards, and editable phase columns. Replace its examples with your own project’s actual state.

Do not imply that an exploratory item is funded or scheduled. State the uncertainty next to the item, where readers will see it.