Documentation for version v1.3.1 is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.
The Velero maintainers use a weekly rotation to manage community support. Each week, a different maintainer is the point person for responding to incoming support issues via Slack, GitHub, and the Google group. The point person is not expected to be on-call 24x7. Instead, they choose one or more hour(s) per day to be available/responding to incoming issues. They will communicate to the community what that time slot will be each week.
We will update the public Slack channel’s topic to indicate that you are the point person for the week, and what hours you’ll be available.
#velero
public Slack channel in Kubernetes orgvelero
, velero-plugin-for-[aws|gcp|microsoft-azure|csi]
, helm-charts
)Generally speaking, new GitHub issues will fall into one of several categories. We use the following process for each:
Enhancement/User
or Enhancement/Dev
New Issues
swimlane for triage by product mgmtBug
New Issues
swimlane for triage by product mgmtInvestigating
Needs Info
label to indicate an issue is waiting for information from the user. Remove/re-add the label as needed.We ensure all GitHub issues worked on during the week on are labeled with Investigating
and Needs Info
(if appropriate), and have updated comments so the next person can pick them up.
To help you get started, see the documentation.