I have raised the same question and suggestion when I started with this project on March.
The answer Jay gave me was that the `master` branch represents the latest release we did.
The intent is that when you check out the code, you'll get something that's been tested and should work -- unlike the development branch that can be potentially broken.
I tried to make it clear to the potential contributors on the http://deltacloud.org/contribute.html page that we develop on the `next` branch. Anyone who follows those instructions should be all set up.
Other reason I was given was that other FOSS projects do it this way and that we should follow the conventions. The few projects that I looked at aren't like that but I admit I have very little experience here.
Personally, I would prefer if `master` was the default development branch with the most recent code and then we'd have a `stable` branch for the latest release. But I don't think it's that much of a deal.
Thomas
----- Original Message ----- From: "Mark McLoughlin" markmc@redhat.com To: "deltacloud-devel" deltacloud-devel@lists.fedorahosted.org Sent: Friday, November 26, 2010 2:46:25 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: [deltacloud-devel] aggregator master branch
Hey,
Just a quick question - what does the master branch of the aggregator repo represent?
I just spent some time trying to find an 'aeolus' repo because the master branch hadn't been updated since October I didn't think to check other branches
My take on this is that the master branch is what people see by default when they check out a repo, so it should be the branch that we expect to be most interesting to folks. Since the aggregator is under such heavy development, I think most people are going to be interested in the development branch
Thanks, Mark.
_______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
deltacloud-devel@lists.fedorahosted.org