Implemented all the discussed changes in https://github.com/jenkins-infra/jenkins.io/pull/2659 . Will appreciate reviews
On Tue, Nov 19, 2019 at 1:40 PM Baptiste Mathus <[email protected]> wrote: > > > On Mon, Nov 18, 2019 at 2:03 PM Oleg Nenashev <[email protected]> > wrote: > >> Personally I think Microsoft Edge (Chromium) should be Level 1 as it will >>> be coming out in January and, as far as I know, will be the default browser >>> for Windows 10 (or at least be used quite a bit). I'd also say that given >>> its Chromium based I'd include that and Chromium together along with >>> Chrome. >> >> What if we add it as Level 2 support for now until it is released? >> I agree we would be interested to support it though it should not be a >> big deal taking the engine under the hood. >> >> +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. >> >> >> @Baptiste Do you mean Level 1 support for IE 11 and Level 3 for older >> versions (w/o -1 version support)? >> Sounds reasonable to me. >> > > Yes. IE11 should be the only version we put in Level 1 IMO, even more > after having re-read https://en.wikipedia.org/wiki/Internet_Explorer_11 but > we should probably put a blurb saying Edge is to be preferred and IE11 will > likely soon be Level 2, given MS plans > https://en.wikipedia.org/wiki/Microsoft_Edge and that Edge is even > already default browser on Windows 10 (and later?!). > > Any older IE release should be Level 2 max, Level 3 maybe, I don't feel > that strongly. > > > > >> >> 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. >>> >> >> +1 for any warnings or administrativemonitors if anyone is willing to >> contribute them. Thanks in advance! >> >> >>> I think Firefox ESR would make sense to support as well >>> >> >> +1 for keeping it as Level 1 as it currently is. >> >> >> >> >> On Friday, November 15, 2019 at 4:24:12 PM UTC+1, Matt Sicker wrote: >>> >>> FWIW, I've written any new JS/HTML/CSS according to caniuse.com and >>> their base line supported level, though that might be fairly conservative >>> (not as conservative as the current Jenkins wiki, though!) >>> >>> On Fri, Nov 15, 2019 at 8:15 AM Daniel Beck <[email protected]> wrote: >>> >>>> I think Firefox ESR would make sense to support as well. Its baseline >>>> is never older than a year IIUC, so should be feasible to have it be >>>> considered supported. >>>> >>>> Showing warnings on the UI when using an unsupported browser would >>>> probably be fairly straightforward as well, and help to inform users. >>>> Perhaps we even distinguish between "outdated based on policy" and >>>> "outdated based on features actually used in core or popular plugins", but >>>> that may end up being too much effort to maintain. >>>> >>>> >>>> Does it actually make sense to still support IE? >>>> >>>> On Fri, Nov 15, 2019 at 10:17 AM Oleg Nenashev <[email protected]> >>>> wrote: >>>> >>>>> 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 [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/976db98b-75be-4e29-9bd4-d5fe6676c674%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/976db98b-75be-4e29-9bd4-d5fe6676c674%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> >>>> >>>> -- >>>> >>>> Daniel Beck >>>> Senior Software Engineer >>>> CloudBees, Inc. >>>> >>>> [image: CloudBees-Logo.png] >>>> >>>> >>>> -- >>>> 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 [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKGPEqv9gaVT%2BX%3DoXT%2Busp3RhA%3DfBgcHaWD0hrt8MPdaQ%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKGPEqv9gaVT%2BX%3DoXT%2Busp3RhA%3DfBgcHaWD0hrt8MPdaQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> >>> >>> -- >>> Matt Sicker >>> Senior Software Engineer, CloudBees >>> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/6ac3cc5a-63df-4ed8-a77a-c6f1610ecdef%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/6ac3cc5a-63df-4ed8-a77a-c6f1610ecdef%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/TV_pLEah9B4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp0kXN%3D1jQ-PDcP_h13L1WJLHUQao9v%2BfkVKXq_3EMSRtg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp0kXN%3D1jQ-PDcP_h13L1WJLHUQao9v%2BfkVKXq_3EMSRtg%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLD84QY8nVAjNzYJ_orTRT1venDxykvozRFENzW37oXedA%40mail.gmail.com.
