On 02/23/2015 08:54 PM, Brian Stinson wrote: > On Feb 23 18:13, Honza Horak wrote: >> I'm about to submit a couple of requests into bugs.c.o to create necessary >> infrastructure for collections from RHSCL-1.2 at least. >> But first I want to make sure about the tag and branches names. >> >> Currently we have some testing build tags: >> scl6-el6-mariadb100-build >> scl7-el7-mariadb100-build >> and branches in dist-git (in sclo project): >> scl-mariadb100-el6 >> scl-mariadb100-el7 >> And the SIG has codename 'sclo'.. >> So, it's kind of messy already in the beginning :) >> >> Thinking about keeping it simple and uniform, what about this way: >> >> Keep 'sclo' as SIG codename to indicate it's combination of SCL on openness >> :) > > +1 from me on this. It makes sense to use the actual sig codename. > >> CBS build tags in format like: >> sclo6-mariadb100-build >> sclo7-mariadb100-build >> and branches in dist-git (in both sclo and rpms projects): >> sclo6-mariadb100 >> sclo7-mariadb100 > > In the client tools, there shouldn't be anything that would hold this > up. As long as we remain consistent we can make the mappings work. > >> >> This mail is to check whether we're fine to go this way or if there are some >> limitations we need to follow. >> >> dist-git and CBS gurus, please, provide your PoV. Thanks! >> >> Honza > > Is your proposal to rename the existing mariadb tags and git branches? Yes, if it is possible -- but only in case it makes no big trouble, which I'm not able to evaluate. Honza