[CentOS-virt] CBS tags hierarchy

Fri Mar 20 10:16:48 UTC 2015
Sandro Bonazzola <sbonazzo at redhat.com>

Il 19/03/2015 15:46, George Dunlap ha scritto:
> 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.

anybody else with comments on above proposal?
Should I open the bug requesting above branches/tags/targets/.... ?

> 
>  -George
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com