Skip to content
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.

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

Proposed release naming guidance from Marketing Committee #39

Closed
FiniteStateGit opened this issue Jan 20, 2022 · 3 comments
Closed

Proposed release naming guidance from Marketing Committee #39

FiniteStateGit opened this issue Jan 20, 2022 · 3 comments

Comments

@FiniteStateGit
Copy link

FiniteStateGit commented Jan 20, 2022

The Marketing Committee submits the following message for Sig-Release's review:

Release Naming Guidance

The use of 'major' and 'point' to describe the type of release is optional, but approved, for shorthand/non-technical descriptions.

Example: ...the last major release...
Example: ...an upcoming point release...

A major release follows the format:
<Last two digits of year>.<Last two digits of month>.<Versioning digit = 0>
A point release re-uses the year and month of the previous major release and increments the versioning digit by one.

Example: A major release in June 2025 would be named 25.06.0
Example: A point release in July 2025 would be named 25.06.1
Example: A second point release in January 2026 would be named 25.06.2
Example: A major release in January 2026 would be named 26.01.0

A major release can be referred to in non-technical descriptions without the versioning digit.

Example: 25.06, in general, would refer to a major release from June 2025.

The marketing committee recommends that friendly names are not used for releases.

@Ulrick28
Copy link
Contributor

Ulrick28 commented Jan 26, 2022

During 1/25 Technical Steering Committee (TSC) meeting, the TSC gave approval for this proposal, though would like SIG-Release to still vote on the topic.

@tonybalandiuk
Copy link
Contributor

can we clarify what we mean by "friendly name" here?

@tonybalandiuk
Copy link
Contributor

this has been approved/accepted. Closing it now although it has been accepted for the past few releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants