[RELEASE] branching and tagging the components

Giulio Fidente gfidente at fedoraproject.org
Tue Nov 20 16:12:15 UTC 2012


hi Steven

On 11/20/2012 05:04 PM, Steve Linabery wrote:
> It's certainly not a 'proper' release, with docs, release announcement, description of what other components are required (factory, et al).

agreed, I was trying to find out if and how the tags/branches of the
components relate to each other (inclunding factory, oz, cli, maybe TIM
at some point in the future)

>> Also, do you see the idea of tagging all the components with the same
>> tag a valid approach or are there different suggestions?
> 
> What I would like to see on an actual upstream release is:
> 1) create maintenance branch and tag on that branch
> 2) bump version number on master branch for ongoing development

to be honest, I'm not sure what are the best practices for such a
complex project where we want to merge the development efforst from
different components, but your looks to me a good approach

devs, any hint on this?
-- 
Giulio Fidente



More information about the aeolus-devel mailing list