Re: LTS baseline selection for the successor of 2.222

+1 for 2.235, assuming that we are conservative about merges this week. On Wednesday, April 29, 2020 at 5:47:41 PM UTC+2, Tim Jacomb wrote: > > 2.235 would also be my preference, I've got 2 (hopefully) last system read > PRs, I would love to get in before the LTS > > On Wed, 29 Apr 2020 at

Re: LTS baseline selection for the successor of 2.222

> On 29. Apr 2020, at 12:44, Oliver Gondža wrote: > > In accordance we recently approved process changes, we are doing next > baseline section two weeks earlier in the cycle. Assuming nobody merges something crazy into core this week, I'm for 2.235. We've moved the baseline decision

Re: Proposal: Making the Hosting team official (and onboarding new members)

+1 on this proposal, I would love to learn and contribute wherever I can. Thanks and stay safe On Wed, Apr 29, 2020, 8:40 PM Oleg Nenashev wrote: > I created a pull request to jenkins.io with the page for the Hosting > team: https://github.com/jenkins-infra/jenkins.io/pull/3142 > > On

Re: LTS baseline selection for the successor of 2.222

+1 from me for 2.235, particularly with the additional UI improvements in recent releases. Also assuming that there will be *lots of help testing the release candidate* once it is delivered . ☺ ☺ ☺ On Wed, Apr 29, 2020 at 9:59 AM Oleg Nenashev wrote: > +1 for 2.235, assuming that we are

RE: Plugin: Liquibase Runner

Hi, Team! Just checking on the PR. As far as I can tell, it’s passed the checks. Slide asked me to attach the thread to the PR and I’ve done that. What’s next? https://github.com/jenkins-infra/repository-permissions-updater/pull/1513 Thanks! Robert -- You received this message because you

Re: Proposal: Making the Hosting team official (and onboarding new members)

I'm a definite +1 on this. More people looking at the requests and such would definitely be helpful and more people means more ideas on how to streamline and improve the process. On Wed, Apr 29, 2020 at 5:38 AM Oleg Nenashev wrote: > Thanks Tim and Marky, > > Any help there will be appreciated,

Re: Proposal: Making the Hosting team official (and onboarding new members)

Great idea! I am +1 for both > On Apr 29, 2020, at 5:02 AM, Marky Jackson wrote: > > For me it is both. +1 for the proposal and +1 to join > >> On Apr 29, 2020, at 5:01 AM, Oleg Nenashev > > wrote: >> >> Hi all. Just to make sure, +1 for the proposal or +1 for

Re: LTS baseline selection for the successor of 2.222

I would also vote for 2.234 for the UI improvements that I think the UX SiG would love to see used more widely and get more feedback about. Thanks! On Wed, Apr 29, 2020 at 2:00 PM Tim Jacomb wrote: > My preference would be 2.234, > > It has the most system read features in it which would be

Re: LTS baseline selection for the successor of 2.222

2.235 would also be my preference, I've got 2 (hopefully) last system read PRs, I would love to get in before the LTS On Wed, 29 Apr 2020 at 14:54, Daniel Beck wrote: > > > > On 29. Apr 2020, at 12:44, Oliver Gondža wrote: > > > > In accordance we recently approved process changes, we are

Re: Proposal: Making the Hosting team official (and onboarding new members)

I'm +1 for formalizing processes and spreading out the load. I'm also volunteering for said team. With the exception of the hosting jira tickets I have been trying to review and reply to emails and chat requests as much as I can On Wed., Apr. 29, 2020, 9:26 a.m. Vlad Silverman, wrote: >

Re: Proposal: Making the Hosting team official (and onboarding new members)

I created a pull request to jenkins.io with the page for the Hosting team: https://github.com/jenkins-infra/jenkins.io/pull/3142 On Wednesday, April 29, 2020 at 4:59:20 PM UTC+2, slide wrote: > > I'm a definite +1 on this. More people looking at the requests and such > would definitely be

Proposal: Making the Hosting team official (and onboarding new members)

Hi all, In the Jenkins community we have an unofficial Hosting team which handles various requests related to plugin hosting (forking/transferring plugins, managing permissions and update center blacklists, etc.) There are multiple contributors involved in this activity on a regular basis,

Re: Proposal: Making the Hosting team official (and onboarding new members)

I think its a good idea to make as many of the teams as possible that are needed to keep Jenkins trucking along official & documented so the proposal makes sense to me. I'm also interested in helping out the team to help spread the load around a bit. Richard. On Wed, 29 Apr 2020 at 21:09, Oleg

Re: Proposal: Making the Hosting team official (and onboarding new members)

Thanks Tim and Marky, Any help there will be appreciated, any bandwidth improvements and higher bus factor would be great. Will wait for feedback from Alex Earl and other contributors before touching permissions, working on guidelines. Everyone is welcome to subscribe to channels (dev mailing

Re: Proposal: Making the Hosting team official (and onboarding new members)

And thanks to Richard! Much appreciated On Wednesday, April 29, 2020 at 2:38:24 PM UTC+2, Oleg Nenashev wrote: > > Thanks Tim and Marky, > > Any help there will be appreciated, any bandwidth improvements and higher > bus factor would be great. > Will wait for feedback from Alex Earl and other

Re: Proposal: Making the Hosting team official (and onboarding new members)

+1 On Wed, 29 Apr 2020 at 10:51, Richard Bywater wrote: > I think its a good idea to make as many of the teams as possible that are > needed to keep Jenkins trucking along official & documented so the proposal > makes sense to me. > > I'm also interested in helping out the team to help spread

Re: Proposal: Making the Hosting team official (and onboarding new members)

This is a great idea and I am a +1 On Wednesday, April 29, 2020 at 2:09:27 AM UTC-7, Oleg Nenashev wrote: > > Hi all, > > > In the Jenkins community we have an unofficial Hosting team which handles > various requests related to plugin hosting (forking/transferring plugins, > managing

Re: Proposal: Making the Hosting team official (and onboarding new members)

+1 to both, although not planning on it being a primary focus, I'll help out where and when I can Thanks Tim On Wed, 29 Apr 2020 at 13:02, Marky Jackson wrote: > For me it is both. +1 for the proposal and +1 to join > > On Apr 29, 2020, at 5:01 AM, Oleg Nenashev wrote: > > Hi all. Just to

LTS baseline selection for the successor of 2.222

In accordance we recently approved process changes, we are doing next baseline section two weeks earlier in the cycle. Let's voice the baseline candidates and concerns so we have the candidate by next Governance meeting at 2020-05-06. My preferable choices would be 2.232 as the next release

Re: LTS baseline selection for the successor of 2.222

My preference would be 2.234, It has the most system read features in it which would be great to announce as part of the next LTS Also 2.233 has the button re-work which really should make it in imo (and 2.234 with the help icon changes) Thanks Tim On Wed, 29 Apr 2020 at 11:44, Oliver Gondža

Re: Proposal: Making the Hosting team official (and onboarding new members)

For me it is both. +1 for the proposal and +1 to join > On Apr 29, 2020, at 5:01 AM, Oleg Nenashev wrote: > > Hi all. Just to make sure, +1 for the proposal or +1 for joining the teams? :) > > On Wed, Apr 29, 2020, 13:58 Marky Jackson > wrote: > This is a

Re: Proposal: Making the Hosting team official (and onboarding new members)

Hi all. Just to make sure, +1 for the proposal or +1 for joining the teams? :) On Wed, Apr 29, 2020, 13:58 Marky Jackson wrote: > This is a great idea and I am a +1 > > On Wednesday, April 29, 2020 at 2:09:27 AM UTC-7, Oleg Nenashev wrote: >> >> Hi all, >> >> >> In the Jenkins community we have