+1 on the update of the policy. All for dropping explicit "support" for older browsers. (support
I love the idea to actually have something like an Administrative warning to tell users that they may see UI quirks given the browser they're using. And that they should feel free to report them iff these quirks are also present on latest browser versions. +1 on supporting temporarily only the very latest version of IE, and maybe have a blurb saying this is planned to be discontinued given MS plans anyway to invest into Edge instead. Le ven. 15 nov. 2019 à 11:44, 'Björn Pedersen' via Jenkins Developers < jenkinsci-dev@googlegroups.com> a écrit : > Hi, > > sounds reasonable in general. > > What another project (https://github.com/indico/indico/releases/tag/v2.2 > ): > >> *Drop support for Internet Explorer 11 and other outdated or discontinued >> browser versions.* Indico shows a warning message when accessed using >> such a browser. The latest list of supported browsers can be found in >> the README <https://github.com/indico/indico#browser-support>, but >> generally Indico now supports the last two versions of each major browser >> (determined at release time), plus the current Firefox ESR. >> > > So support one version back at level 1 ( this means also that before > using bleeding edge browser features they have settled for at least on > release). > > I suggest to also add a js warning plugin (e.g. > https://github.com/outdatedbrowser/outdated-browser) to jenkins to give > the users a better feedback for unsupported browsers. > > Björn > > > Am Freitag, 15. November 2019 10:17:10 UTC+1 schrieb Oleg Nenashev: >> >> Hi all, >> >> There was recently a question about Jenkins browser support policy raised >> in the chats. Currently the policy is hosted on Wiki (here >> <https://wiki.jenkins.io/display/JENKINS/Browser+Compatibility+Matrix>), >> and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully >> supported, ouch. It does not look like we had any major changes since the >> inception of the policy in 2014. I have created a pull reques >> <https://github.com/jenkins-infra/jenkins.io/pull/2649>t to move the >> policy to jenkins.io, and I would like to make some changes to actualize >> it. >> >> What do I propose? >> >> - Chrome, Firefox, IE, Safari >> - Level 1: >> - "Latest regular release, latest minor release / patch level" >> - Level 2: >> - Previous patches of the latest regular release >> - Latest minor release / patch level for the "Version -1" >> - Level 3: >> - All other versions >> - Other browsers, including mobile versions, Chromium, Microsoft >> EDGE, etc.: >> - Level 2: Latest regular release, latest minor release / patch >> level >> - Level 3: All other versions >> >> >> This policy should be somewhat aligned with the current ATH state. IIUC >> we test only Firefox now, and there is a PR by Oliver Gondza to run tests >> on Chrome instead (here >> <https://github.com/jenkinsci/acceptance-test-harness/pulls>) >> >> WDYT? >> >> Best regards, >> Oleg >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/97fa0774-e4a3-4698-bfc4-94006dd51af2%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/97fa0774-e4a3-4698-bfc4-94006dd51af2%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5vxUiUchuVyYkaoGQ9peM%3D8H%2BbRy7dZpUXziNMji1TKQ%40mail.gmail.com.
