The Releases page (/code/releases, Releases in the Code rail) shows what the BlockoutGames organization published on GitHub and how often each repository ships. Every signed-in member can read it. The old address /releases opens it. These are GitHub releases of code, not a game's release state in the studio.
Which releases the Releases page counts
The range switch offers 30 days, 90 days (the default), 1 year and all. The range starts with its first whole week (Sunday, UTC), as the weekly chart does. Counts and charts use published releases only; drafts are listed in the timeline but never counted. Pre-releases count as releases. Definitions: Releases, days between releases.
The Releases page's tiles
- Releases in the rangereleases
The coral tile: published releases in the range; its line says how many drafts were left out.
- Repositories releasingrepositories
How many repositories published at least one release in the range.
- Median days betweendays
The median gap between consecutive published releases across the whole organization in the range. It needs two releases.
- Latest release
How long ago the newest one was published, with its repository and tag.
Releases per week
Published releases per week, stacked by repository: the seven repositories with the most releases are named, the rest are Other repositories. Drafts are not counted.
Release cadence by repository
Release cadence ranks repositories by the median number of days between their published releases, most frequent first, over all recorded history whatever the range. Each bar shows how many releases the repository has had and when the latest was, and opens the repository's page. Repositories with only one release are named under the chart (One release so far).
The release timeline
Release timeline lists every release and draft in the range, newest first, up to 40. Each entry shows the date, the release's name (opens it on GitHub), its tag when the name differs, a Pre-release or Draft badge, the repository (opens its page), when it was published or drafted, and the first three lines of its notes. With more than 40 in the range, the card says how many there are; the rest are on GitHub.
How fresh the Releases page is
The page reads the latest GitHub snapshot, collected every 30 minutes; the header says Collected … ago. A release published on GitHub appears after the next collection. See Code.
The Releases page on a phone
Tiles sit two to a row; the weekly chart, the cadence and the timeline follow one under another at full width. In the timeline the date sits above each release instead of beside it.
Every card here can be put on your home page with Add to a page. You are notified when a release is published; see Notifications.
Updated