[WIP] Update version release policy

[JesseStutler]

Superseded by #147 (re-opened from fork as the original was accidentally pushed to the upstream repository).

[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.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Marked as WIP for community discussion.

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 hzxuzhonghu 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 significantly updates the version-release.md document to provide a more detailed and structured explanation of Volcano's versioning, release cadence, planning, stabilization, patch releases, and supported versions. The review feedback focuses on minor grammatical and phrasing improvements to make the English text more idiomatic and professional, such as replacing "classical scenes" with "typical scenarios", hyphenating "Release-related", and capitalizing "Docker".

[gemini-code-assist]

Using 'depending on project status' is more idiomatic than 'according to project status'.

Suggested change

	Volcano projects may follow different release cadences according to project
	status, user requirements, and community discussion.
	Volcano projects may follow different release cadences depending on project
	status, user requirements, and community discussion.

[gemini-code-assist]

The phrase 'feedback of community' is grammatically awkward, and 'classical scenes' is a literal translation of a Chinese idiom (经典场景) that is better translated as 'typical scenarios' or 'common use cases' in English.

Suggested change

	According to the feedback of community, we will collect requirements from
	classical scenes or common demands. Requirements can also come from open issues,
	According to community feedback, we will collect requirements from
	typical scenarios or common demands.

[gemini-code-assist]

The compound modifier 'Release related' should be hyphenated as 'Release-related' for proper grammar.

Suggested change

	Release related bug fixes, regression fixes, security fixes, documentation
	Release-related bug fixes, regression fixes, security fixes, documentation

[gemini-code-assist]

'Docker' is a proper noun and should be capitalized.

Suggested change

	archives, release notes, docker images, charts, or packages according to the
	archives, release notes, Docker images, charts, or packages according to the