Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

2017 05:20 To: Frank Brockners (fbrockne) <fbroc...@cisco.com>; Trevor Bramwell <tbramw...@linuxfoundation.org> Cc: Serena Feng <feng.xiao...@zte.com.cn>; opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

+1 Jose > On 08 Dec 2017, at 01:01, Fatih Degirmenci > wrote: > > Hi Releng Committers, > > During OPNFV Plugfest, we had conversations around having committer list per > Releng repository/Gerrit Project. > > The reason behind this is that, Releng

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

Sent: Sonntag, 10. Dezember 2017 15:34 To: Fatih Degirmenci <fatih.degirme...@ericsson.com> Cc: Serena Feng <feng.xiao...@zte.com.cn>; opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository +1

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

Subject: Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository +1 Giving leaders of subproject the freedom to manage +2 rights on their own repository will be very helpful for ensuring patches are reviewed by those with the correct competencies and merged in a timely manner. Pe

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

+1 Giving leaders of subproject the freedom to manage +2 rights on their own repository will be very helpful for ensuring patches are reviewed by those with the correct competencies and merged in a timely manner. Perhaps having a 'mini-info' file in each repository would help track this, intead

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

Only caveat I have is that there are no committers (or regular reviewers) to releng-anteater to get patches landed. With that in mind though, I don't mind moving the project back to github (where its easier for anyone to patch) and we keep all the project exception files in releng (where it would

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

+1 On 12/08/2017 12:01 AM, Fatih Degirmenci wrote: > Hi Releng Committers, > >   > > During OPNFV Plugfest, we had conversations around having committer list > per Releng repository/Gerrit Project. > >   > > The reason behind this is that, Releng project currently has 5 different >

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

+1 From: opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of Fatih Degirmenci Sent: Friday, December 8, 2017 2:01:34 AM To: Aric Gardner; Tim Rozet; Morgan Richomme; Jose

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

I consider this proposal as very good regarding the multiple different skills involved in the current releng tree. Functest could leverage on it too as it will incubate requirements and xtesting which could differ on interests and skills. Switching to a dedicated project will cost at least to

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

+1 Good idea, will each repo need an INFO file, or will we track the committers by sub project in the parent repo? On Thu, Dec 7, 2017 at 7:01 PM, Fatih Degirmenci wrote: > Hi Releng Committers, > > > > During OPNFV Plugfest, we had conversations around having

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

Hi Ryota, Introducing sub-team lead was part of our conversation today and we will work on it when/if our proposal gets agreed within Releng project and approved by TSC. /Fatih From: Ryota Date: Thursday, 7 December 2017 at 16:16 To: Fatih Degirmenci

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

+1 Also we need to consider long term transition. Each repo or sub-team would be getting bigger then could be independent project/repo eventually. So, it would be nice to find sub-team lead or key person who is responsible in each repo along with this list modification. Just two cents though.