Re: 2019 Elections: voting has begun

Seems that will adding it additional registrants to the poll, the whole csv list was added which resulted in resend of the votes. Fortunately it does not mess up the votes for those who have already voted. (Adding to list of things for the retro...) Tracy On Fri, Nov 15, 2019 at 3:46 PM Richard

Re: 2019 Elections: voting has begun

Ah good to know. Didn't want to click on the links in case it messed things up :) Richard. On Sat, 16 Nov 2019, 9:42 AM Slide, wrote: > I received the same thing, but when I clicked on the links, it said I had > already voted. > > On Fri, Nov 15, 2019, 13:37 Richard Bywater wrote: > >> A few

Re: 2019 Elections: voting has begun

I received the same thing, but when I clicked on the links, it said I had already voted. On Fri, Nov 15, 2019, 13:37 Richard Bywater wrote: > A few hours ago I received another three poll emails even though I > previously had voted. Is that expected and/or should I revote? > > Richard. > > On

Re: Where to place utility code used in several plugins?

On Fri, Nov 15, 2019 at 12:57 PM Ullrich Hafner wrote: > What is the preferred way of handling theses classes? Should I create two new > modules (util and plugin-utill) that will host theses classes? Keep it simple. The latter should be a plugin (`hpi`), and both should be hosted in @jenkinsci.

Re: 2019 Elections: voting has begun

A few hours ago I received another three poll emails even though I previously had voted. Is that expected and/or should I revote? Richard. On Wed, 13 Nov 2019, 12:52 PM Kohsuke Kawaguchi, wrote: > The voting has begun! It'll remain open until Nov 24th 5pm PT. > > If you have already

Where to place utility code used in several plugins?

I have some classes that I would like to use in several of my Jenkins plugins. Some classes are depending on Jenkins core, some classes only use JRE dependencies. Up to now I duplicated these classes by copying them into the corresponding plugins - but this is ugly and error prone. What is

Re: Modularization of UI modules

I just to report back here on how I finally implemented the modularization of the JS modules: for each JS dependency I created a new api plugin that contains the WebJar of the JS library and some utility classes. So other plugins can use these dependencies as well now. The resulting plugin

Re: 2019 Elections: voting is delayed

Found https://issues.jenkins-ci.org/browse/INFRA-2319 On Friday, November 15, 2019 at 5:26:56 PM UTC+1, Jakub Bocheński wrote: > > Hi, I tried to register > After recovering the email from my spam folder I clicked "I want to > participate" but I get an error > > > Your participation can't be

Re: 2019 Elections: voting is delayed

Hi, I tried to register After recovering the email from my spam folder I clicked "I want to participate" but I get an error > Your participation can't be confirmed, please contact a Jenkins administrator Is this the right place to "contact a Jenkins administrator"? -- You received this

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: speed your Jenkins by an adapter of Jenkins update center

What I'm talking about is not the internal mirror. The mirror is public. I just set up one mirror on GitHub which is https://github.com/jenkins-zh/update-center-mirror/tree/master/tsinghua. On Fri, Nov 15, 2019 at 7:46 PM Oliver Gondža wrote: > I suspect few people would bother to report

Re: speed your Jenkins by an adapter of Jenkins update center

I suspect few people would bother to report (accurate) numbers there. Setting up internal mirror is the part that needs to be done and this is the kind of bonus task that always gets outprioritized. IMO. On 15/11/2019 12.14, Rick wrote: Hi Björn, It's true that those download statistics

Re: speed your Jenkins by an adapter of Jenkins update center

Hi Björn, It's true that those download statistics cannot be count. What about building a third party statistic site. And we can publish this data besides the official one as a reference. What do you think about this? Best, Rick On Fri, Nov 15, 2019 at 6:52 PM 'Björn Pedersen' via Jenkins

Re: speed your Jenkins by an adapter of Jenkins update center

Hi, So the idea is to omit the round-trip to the main update center on each download. Community-wise this has one downside: all those downloads then do not show up in the download statistics. But the same is true for all fully private mirrors behind firewalls that serve updatecenter.json

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