Skip to content

RELEASES: finalise policy #5050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cyphar wants to merge 2 commits into
base: main
Choose a base branch
from
Open

RELEASES: finalise policy #5050

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c150f4
RELEASES: remove 'draft' section of policy
cyphar Nov 28, 2025
bf258ce
RELEASES: remove <= 1.1.x special casing
cyphar Nov 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 0 additions & 14 deletions RELEASES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,6 @@ formally guarantee that API compatibility will be preserved.

### Release Cadence ###

> **NOTE**: At time of writing, this proposal is still a draft as we have not
> yet done several releases using this cadence. If you have feedback on this
> proposal (such as how well this proposal addresses your needs as a downstream
> packager of runc), please feel free to [open an issue][new-issue] so we can
> discuss it further. However, the current plan is for this proposal to be
> followed for the `1.3.0` and `1.4.0` releases in 2025.

[new-issue]: https://github.com/opencontainers/runc/issues/new/choose

runc follows a 6-month minor version release schedule, with the aim of releases
Expand Down Expand Up @@ -68,13 +61,6 @@ Here is a hypothetical release timeline to see how this works in practice:

### Support Policy ###

> **NOTE**: The following policy provides much longer support guarantees than
> we have historically provided for older runc releases. In order to avoid
> adding new support guarantees for old runc versions we have long-since
> stopped supporting, the following support policy only applies for runc
> releases from `1.2.0` onwards. In other words, runc `1.1.0` and `1.0.0` are
> not guaranteed support by this policy.

In order to ease the transition between minor runc releases, previous minor
release branches of runc will be maintained for some time after the newest
minor release is published. In the following text, `latest` refers to the
Expand Down