Re: Proposal: Jenkins Browser Support policy updates

The policy change has been approved by the Governance meeting. Taking the consensus here, I went ahead and merged https://github.com/jenkins-infra/jenkins.io/pulls Thanks all! On Tuesday, November 19, 2019 at 11:42:46 PM UTC+1, Oleg Nenashev wrote: > > Since we have a Governance meeting

Re: Proposal: Jenkins Browser Support policy updates

Since we have a Governance meeting tomorrow, I have added this topic to the agenda so that we can formally confirm the changes https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-November20 On Tuesday, November 19, 2019 at 2:07:53 PM UTC+1, Oleg Nenashev

Re: Proposal: Jenkins Browser Support policy updates

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 wrote: > > > On Mon, Nov 18, 2019 at 2:03 PM Oleg Nenashev > wrote: > >> Personally I think Microsoft Edge (Chromium) should

Re: Proposal: Jenkins Browser Support policy updates

On Mon, Nov 18, 2019 at 2:03 PM Oleg Nenashev 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

Re: Proposal: Jenkins Browser Support policy updates

> > 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

Re: Proposal: Jenkins Browser Support policy updates

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 wrote: > I think Firefox ESR would make sense to

Re: Proposal: Jenkins Browser Support policy updates

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.

Re: Proposal: Jenkins Browser Support policy updates

+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

Re: Proposal: Jenkins Browser Support policy updates

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

Re: Proposal: Jenkins Browser Support policy updates

On 15/11/2019 10.17, Oleg Nenashev 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 ), and the policy looks to be REALLY

Re: Proposal: Jenkins Browser Support policy updates

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

Proposal: Jenkins Browser Support policy updates

Hi all, There was recently a question about Jenkins browser support policy raised in the chats. Currently the policy is hosted on Wiki (here ), and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully