[RELEASE] branching and tagging the components

Steve Linabery slinaber at redhat.com
Tue Nov 20 16:04:36 UTC 2012


On Tue, Nov 20, 2012 at 11:38:17AM +0100, Giulio Fidente wrote:
> hi there,
> 
> I'm trying to figure out how the branches/tags applied to the components
> on github match a release.
> 
> I tried to figure out it myself but I'm need of some help and I thought
> that discussing this on the list was good idea.
> 
> My purpose is to find out which branch/tag one should checkout to make
> sure that all the required components will work well together.
> 
> Here (which I think is outdated):
> 
> https://redmine.aeolusproject.org/redmine/projects/aeolus/wiki/Development_Setup
> 
> we suggest to check out the components from master but that can't be a
> fixed release in time.
> 
> Literature suggests to tag all the components with the same tag to mark
> a release but to do this once (and move forward from that point), we
> firstly need to find out how the existing tags match to each other, and
> this is my question indeed.
> 
> If I wanted to checkout today the sources for some 'stable' release,
> what should I do?

At the end of the last sprint, I tagged with '2012.10.Sprint1' on the conductor, aeolus-configure, aeolus-image-rubygem, and aeolus-cli repos.

These should define a setup at least as stable as we were at the end of the sprint, but I can't say with certainty whether that represents a 'stable release'.

It's certainly not a 'proper' release, with docs, release announcement, description of what other components are required (factory, et al).

> 
> 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

And then the additional documentation/website/announcement tasks alluded to above.

Thanks for raising the issue. Let's discuss it here and in next release cabal meeting.

s|e
> -- 
> Giulio Fidente



More information about the aeolus-devel mailing list