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.

A repo that is not atomically synchronized with my sources means I
can't take full responsibility.

> 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
> bkorren@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/

> _______________________________________________
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel