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

Add Document Conventions file to Getting Started section #702

Merged

Conversation

jillian-maroket
Copy link
Contributor

@jillian-maroket jillian-maroket commented Jan 6, 2025

Related comment: harvester/release-notes#35 (comment)

Scope:

  • Create "Document Conventions" file with three sections: Release Labels, Feature Labels, Admonitions
  • Write definitions for labels and terms in each section

Notes for reviewers:

  • Are the definitions correct?
  • Can users install the latest version in production? I'm asking because the Support Matrix says "Use Latest versions for test purposes only."
  • Should I add the label Stable to the navbar dropdown list? Example: v1.3 (Stable)

@jillian-maroket jillian-maroket changed the title Add Document Conventions file to v1.5 Add Document Conventions file to Getting Started section Jan 6, 2025
Copy link

github-actions bot commented Jan 6, 2025

Name Link
🔨 Latest commit e25e544
😎 Deploy Preview https://67a2e17c96a476bbdd9e6134--harvester-preview.netlify.app

@jillian-maroket jillian-maroket marked this pull request as ready for review January 7, 2025 08:18
Signed-off-by: Jillian <[email protected]>
@jillian-maroket jillian-maroket self-assigned this Jan 7, 2025

## Release Labels

Harvester has a 26-week release cycle and an N - 1 support policy. Each release is supported for 14 months (12 months of support and 2 months for upgrades). Only the two most recent minor versions receive security and bug fixes. For more information, see the [Support Matrix](https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@innobead I think we should change this for 1.5.0 accordingly. The release cycle is tuned to a 4-month pace. And maybe also mention the community versions vs prime versions?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we should.

@jillian-maroket
Copy link
Contributor Author

@bk201 Please review again. I updated the text to align with what we have in the Longhorn doc.

Copy link
Member

@bk201 bk201 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good on the terminology. I guess we can edit the support length when prime plan starts.

@jillian-maroket jillian-maroket merged commit 03a2ad0 into harvester:main Feb 5, 2025
3 checks passed
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

Successfully merging this pull request may close these issues.

3 participants