Keeping the Velero issue triage clean

[Wesley Hayutin]

Greetings,

Hoping to get your thoughts on taking some steps to keep the Velero issues free of downstream product issues.  The goal here is to save developers time in not having to triage issues created from the various downstream products and are inappropriate for an upstream issue tracker.

The thought would be to add a little documentation and links in the troubleshooting section [1] of the documentation that points to Tanzu, OpenShift, PowerProtect, Azure, etc links.

ATM, I count 13 velero bugs that reference OADP.  Probably not something non Red Hat folks need to spend time with.  There are also many issues that reference openshift but that could be a valid upstream install.

Just a thought, WDYT?

[1] https://velero.io/docs/v1.13/troubleshooting/#general-troubleshooting-information

[Tiger Kaovilai]

Being addressed in Update README to clarify the scope of issues. by reasonerjt · Pull Request #7717 · vmware-tanzu/velero (github.com)

--
You received this message because you are subscribed to the Google Groups "Project Velero" group.
To unsubscribe from this group and stop receiving emails from it, send an email to projectveler...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectvelero/5ca5a50f-f9c3-4ab0-8eb7-7579ee26d332n%40googlegroups.com.