upstream/k3s
1
0
Fork 0
mirror of https://github.com/k3s-io/k3s.git synced 2025-12-18 23:06:14 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
k3s/ROADMAP.md
Ben ade82387f7
Inclusive naming proposal (issue: #12110, Orlin Vasiliev) (#12383) 
* Inclusive naming proposal (issue: #12110, Orlin Vasiliev)

Basic renaming from 'master' to 'main' as primary branch according to https://github.com/cncf/foundation/blob/main/code-of-conduct.md#our-standards

Signed-off-by: Andrea Benini <andreabenini@gmail.com>
Signed-off-by: Derek Nola <derek.nola@suse.com>

* Additional replacement of master with main in E2E testing, Github Action workflows

Signed-off-by: Derek Nola <derek.nola@suse.com>

---------

Signed-off-by: Andrea Benini <andreabenini@gmail.com>
Signed-off-by: Derek Nola <derek.nola@suse.com>
Co-authored-by: Derek Nola <derek.nola@suse.com>
2025-09-24 08:52:28 -07:00

804 B
Raw Permalink Blame History

Roadmap

The k3s project uses GitHub Milestones to track the progress of changes going into the project.

The k3s release cycle moves in cadence with upstream Kubernetes, with an aim to have new minor releases out within 30 days of upstream .0 releases. To follow incoming changes, watching the Backlog and Current Development GitHub Projects is the most up to date way to see what's coming in upcooming releases.

The development of k3s itself happens in the main branch, which correlates to the most recent Kubernetes minor release. These changes are then backported to the active release lines (at this time, release-[N], release-[N-1], and release-[N-2])