Update version release policy

[JesseStutler]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Update the version release document to match the current Volcano release practice.

This PR covers:

• release cadence for Volcano, Kthena, and other projects with flexible release timing;
• X.Y.Z version meaning;
• rolling version planning through community discussion, GitHub Projects, issues, milestones, or roadmap docs;
• release branch and stabilization wording without claiming a strict code freeze or beta test process;
• patch release scope and supported release branches;
• backport rules for important bug fixes, security fixes, and low-risk compatibility fixes.

Replaces #137 (re-opened from fork).

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[volcano-sh-bot]

@JesseStutler: The label(s) kind/documentation cannot be applied, because the repository doesn't have them.

Details

In response to this:

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Update the version release document to match the current Volcano release practice.

This PR covers:

• release cadence for Volcano, Kthena, and other projects with flexible release timing;
• X.Y.Z version meaning;
• rolling version planning through community discussion, GitHub Projects, issues, milestones, or roadmap docs;
• release branch and stabilization wording without claiming a strict code freeze or beta test process;
• patch release scope and supported release branches;
• backport rules for important bug fixes, security fixes, and low-risk compatibility fixes.

Replaces #137 (re-opened from fork).

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign thor-wl for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Code Review

This pull request updates the version-release.md documentation to comprehensively detail the Volcano community's release planning, versioning scheme, release cadence, branch management, stabilization, patch releases, and supported versions. The review feedback suggests minor improvements to the documentation, including correcting "user cases" to "use cases", capitalizing "Docker", and consistently formatting the master branch name with backticks.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The term 'user cases' is non-standard in this context. It should be 'use cases' to refer to the software engineering concept of use cases.

Suggested change

	Requirements are collected from common user scenarios, open issues, pull
	requests, user cases, compatibility work, and maintainer proposals. The release
	Requirements are collected from common user scenarios, open issues, pull
	requests, use cases, compatibility work, and maintainer proposals. The release

[gemini-code-assist]

For consistency with other branch names, the master branch should be enclosed in backticks.

Suggested change

	Normal development may continue on master during the release period.
	Normal development may continue on `master` during the release period.

[gemini-code-assist]

Proper nouns like 'Docker' should be capitalized.

Suggested change

	We will publish every official release and related artifacts, such as source
	archives, release notes, docker images, charts, or packages according to the
	We will publish every official release and related artifacts, such as source
	archives, release notes, Docker images, charts, or packages according to the

[gemini-code-assist]

For consistency with other branch names like release-1.13, the master branch should also be enclosed in backticks.

Suggested change

	maintained for master, `release-1.13`, `release-1.12`, and `release-1.11`. After
	`release-1.14` is published, the maintained branches become master,
	maintained for `master`, `release-1.13`, `release-1.12`, and `release-1.11`. After
	`release-1.14` is published, the maintained branches become `master`,