On Sun, Feb 5, 2017 at 10:17 AM, Martin Sivak <[email protected]> wrote:
> Hi, > > > The fact that this is specified in the 'jenkins' repo **does not place > > this outside the maintainers` responsibility**. > > A repo where I do not have commit rights means I can't take full > responsibility. > About this, nothing prevent to give merge rights to project maintainers I think. > A repo that is not atomically synchronized with my sources means I > can't take full responsibility. > I think bkorren is working toward this. > > > We actually have an initiative to move this information to the project > > repos. I've started with asking on devel list about how to specify > > this as part of Standard-CI [1]. But have received little topical > > response so far. > > [1]: http://lists.ovirt.org/pipermail/devel/2017-January/029161.html > > You've got enough responses already to propose a different schema than > fixed branch names. Just give us a config file. Seriously, stop > reinventing the wheel and take a look at how others are doing it > (distgit, travis, tito, ...). > > Martin > > > > > -- > > Barak Korren > > [email protected] > > RHCE, RHCi, RHV-DevOps Team > > https://ifireball.wordpress.com/ > > _______________________________________________ > > Devel mailing list > > [email protected] > > http://lists.ovirt.org/mailman/listinfo/devel > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
