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 our support matrix links to welcome #796

Open
aburdenthehand opened this issue May 10, 2024 · 3 comments
Open

Add our support matrix links to welcome #796

aburdenthehand opened this issue May 10, 2024 · 3 comments
Labels
good-first-issue Identifies an issue that has been specifically created or selected for first-time contributors. hacktoberfest Categorizes as a Hacktoberfest contribution kind/bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@aburdenthehand
Copy link
Member

What happened:
Background: A question was asked in our Community Meeting this week (May 8th, 2024) about what versions of KubeVirt we support, and where the "EOL" support line is drawn (in the meeting I said that my understanding was We support the last three versions as per our support matrix and any older versions fall into the category of "if someone from the community feels personally compelled or invested to help out with the issue then they might, but it cannot be expected". When asked this distinction was documented somewhere, we couldn't find it in the meeting. But that's because we didn't look in kubevirt/kubevirt/docs/kubernetes-compatibility.md, a file that predates our support matrix and could do with a bit of an update.

I propose that we:

  • update kubernetes-compatibility.md to point to our support matrix and whatever other housekeeping update is required.
  • Add the relevant text (#support-extensions) to our support matrix.
  • Add this info to our user-guide in docs/index.md#getting-help -> because the question of 'Is your version of k8s+kubevirt supported?' is an oft-asked first step to troubleshooting

This touches 3 repos (hooray) but it can probably be safely all tracked here. (But if someone wants to raise the appropriate bugs in those other repos then you are of course welcome.)

FYI @EdDev @orelmisan @larrydewey

@aburdenthehand aburdenthehand added good-first-issue Identifies an issue that has been specifically created or selected for first-time contributors. kind/bug labels May 10, 2024
@anishbista60
Copy link

@aburdenthehand Can i work on this issue or it is for Kubevirt member only ?

@aburdenthehand
Copy link
Member Author

@anishbista60 sorry for the delay. You are very welcome to work on this!

@aburdenthehand aburdenthehand added the hacktoberfest Categorizes as a Hacktoberfest contribution label Oct 3, 2024
@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good-first-issue Identifies an issue that has been specifically created or selected for first-time contributors. hacktoberfest Categorizes as a Hacktoberfest contribution kind/bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants