argoproj / argo-cd

Declarative Continuous Deployment for Kubernetes
https://argo-cd.readthedocs.io
Apache License 2.0
18.03k stars 5.5k forks source link

Implement a browser support policy #5588

Open dcherman opened 3 years ago

dcherman commented 3 years ago

Filing this for tracking implementation in ArgoCD, but see discussion in https://github.com/argoproj/argo-workflows/issues/5185

jessesuen commented 3 years ago

FWIW, grafana, which is much more heavily browser focused, only provides support at the vendor level and not version:

https://github.com/grafana/grafana/blob/f8c73bdc3fa1e8d031d977e68047a735023d26a5/docs/sources/installation/requirements.md#supported-web-browsers

We should be careful about not making promises that we can't keep.

dcherman commented 3 years ago

I think that's perfectly acceptable. The primary goal is twofold - give consumers an idea of what browsers they should expect full support in, but also to give contributors an idea of what browsers we need to target when using newer browser features and when testing changes.

Keeping the browser support policy minimal like you mentioned accomplishes both of those things. We can see if there is demand for different or older browsers after the initial implementation and go from there.

The only modification I'd suggest is that Grafana actually does mention a specific version, and that is the "Current" version of each. I'd suggest we use similar if not the same wording to avoid any confusion about what level of support we're providing for each vendor/browser.