Guide to Chromium Dash: Tracking Releases and Milestones

This article provides a comprehensive overview of Chromium Dash, the official web portal used to monitor the development and release lifecycle of the Chromium web browser. It explains what the platform is and details how software developers, testers, and release managers use its tools to track crucial branch dates, pinpoint specific commit positions, and monitor upcoming release milestones across different operating systems and release channels.

What is Chromium Dash?

Chromium Dash is a centralized web dashboard provided by the Chromium project to give developers and the public visibility into the browser's release schedule and active versions. It replaced an older set of tools, most notably OmahaProxy, consolidating various tracking utilities into a single, modern interface.

The portal aggregates real-time data regarding the state of the Chromium codebase and displays the current versions deployed across all release channels—Canary, Dev, Beta, and Stable. It covers all major platforms, including Windows, macOS, Linux, Android, iOS, and ChromeOS.

Tracking Release Milestones

Chromium operates on a rapid release cycle, where every major version is referred to as a "milestone" (e.g., M120, M121). Chromium Dash simplifies milestone tracking through its Schedule view.

  • Current Status: Developers can immediately see which milestone is currently in the Stable, Beta, or Dev channel.
  • Future Planning: The portal lists upcoming milestones months in advance. This allows developers to plan feature rollouts, origin trials, and API deprecations around exact release windows.
  • Platform Specifics: Because mobile and desktop releases can occasionally diverge by a day or two, the dashboard breaks down milestone rollout dates by specific operating systems.

Monitoring Branch Dates

In Chromium development, all new code initially lands on the main trunk (seen in the Canary channel). To prepare a milestone for a stable release, release managers "cut a branch" from the trunk. Once a branch is cut, only critical bug fixes are merged into it, while new features continue on the main trunk for the next milestone.

Chromium Dash helps developers navigate this process by highlighting key branch dates:

  • Feature Freeze: The date by which all new features for a milestone must be functionally complete.
  • Branch Point: The exact date and time when the release branch is created from the main trunk.
  • Beta Promotion: The date the branch moves to the Beta channel for wider public testing.
  • Stable Cut: The final deadline for critical fixes before the milestone is pushed to the general public.

Knowing the exact branch date tells a developer whether their recently submitted code made it into the upcoming release automatically, or if they need to request special permission to merge their code into the newly created branch.

Identifying Commit Positions

While Chromium uses Git for version control (which relies on randomized alphanumeric hashes), the project also assigns a sequential number called a "commit position" to every change that lands on the main branch. This makes it easy to determine the chronological order of code changes.

Chromium Dash provides specific lookup tools to manage and track these commit positions:

  • Commit Lookup: Developers can paste a Git hash, a bug number, or a commit position into the portal to find out which milestone first included that specific code change.
  • Version Comparison: If a bug appears in a new browser version, developers can input the "last known good" version and the "first known bad" version into Chromium Dash. The portal uses the commit positions of both versions to generate a complete list of every code change that occurred between them, drastically speeding up the debugging process.
  • Branch Base Commits: For every milestone listed on the dashboard, Chromium Dash displays the exact commit position where the branch was cut. If a developer's code has a lower commit position number than the branch base, they know for certain their code is included in that milestone.