Il 20/03/2015 11:29, Karanbir Singh ha scritto: > On 03/19/2015 02:46 PM, George Dunlap wrote: >> On Thu, Mar 19, 2015 at 2:39 PM, Karanbir Singh <mail-lists at karan.org> wrote: >>> On 03/19/2015 12:23 PM, George Dunlap wrote: >>>> On Thu, Mar 19, 2015 at 12:20 PM, Sandro Bonazzola <sbonazzo at redhat.com> wrote: >>>>> Hi, >>>>> following Cloud SIG example[1] I would like to start defining the CBS tags hierarchy for Virt SIG. >>>>> >>>>> For opening the discussion I suggest: >>>>> >>>>> - virt${release}-common : packages not related to xen or kvm, used by at least 2 projects >>>>> - virt${release}-xen : xen hypervisor related packages >>>>> - virt${release}-kvm : kvm hypervisor related packages (like qemu-kvm-ev) >>>>> - virt${release}-ovirt : ovirt packages and dependencies, not required by other projects >>>>> - virt${release}-docker : docker packages and dependencies, not required by other projects >>>> >>>> Looks reasonable at first blush. >>>> >>>> -George >>>> _______________________________________________ >>>> CentOS-virt mailing list >>>> CentOS-virt at centos.org >>>> http://lists.centos.org/mailman/listinfo/centos-virt >>>> >>> >>> note that we want git branch, koji builds, release tags and test >>> project, sign request queue and release process to map to a single >>> 'TAG', will this still work ? >> >> I think so... I'm not sure what else we might want. >> > > how would we sync the different branch names ? > > note: the proposal here is going to result in ~ 24 different branches > for each target ( into git.centos.org ) > We can reduce it a bit, just keeping virt7-ovirt instead of virt${release}-ovirt; no plan to get it on el6 right now. We can also drop common if we decide to provide the same rpm in 2 or more different projects repo. I'm not sure it's wise to do the same for the kvm target. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com