Agreed that it is best to have the Apache pre-commit build run successfully before merging.
-Flavio > On 09 Jun 2017, at 11:12, Enrico Olivelli <eolive...@gmail.com> wrote: > > 2017-06-09 11:06 GMT+02:00 Flavio Junqueira <f...@apache.org>: >> I just checked the configuration in jenkins and the retention of a build is >> currently 14 days and no max number of jobs. That should be sufficient, >> otherwise we might end up overwhelming jenkins. >> > > Yet I think that actual configuration is ok from this point of view. > > As we have decided to start using github issues more permissions > should be given to committers or at least to PMCs > > I think that PR are indeed "issues" for GitHub > > If you think it is not the case I'm fine anyway. > > Usually I run tests on my laptop before approving or merging patches > > >> -Flavio >> >>> On 09 Jun 2017, at 10:58, Flavio Junqueira <f...@apache.org> wrote: >>> >>> I can increase retention if that helps. >>> >>> -Flavio >>> >>>> On 09 Jun 2017, at 10:51, Enrico Olivelli <eolive...@gmail.com> wrote: >>>> >>>> Hi, >>>> I would like to ask infra permissions to edit pull requests of other >>>> users, at least "close"/"reopen" to force automatic QA. >>>> >>>> We have a short backlog of PR QA builds so after some time it is not >>>> possible to see old tests results >>>> >>>> Maybe this permission can be extended automatically to every committer >>>> of the project. >>>> >>>> I think that not every of us (committers) has bound his github account >>>> to the apache id, in fact when you are "linked" in the comments on PRs >>>> you are listed as "member", otherwise as "contributor") >>>> >>>> Thoughts ? >>>> >>>> Enrico >>> >>
