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.
Hi Mark,
I have the same opinion. Would make more sense to have the development on master branch and tag stable releases with tags.
+1 for moving to master :)
-- Ladislav
On Nov 26, 2010, at 2:46 PM, Mark McLoughlin wrote:
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
On 11/26/10 - 01:46:25PM, Mark McLoughlin wrote:
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
Yeah, as others have mentioned, we do most of the development on next, and then, in theory, sync over to master when we have something stable. This is the inverse of doing everything important on master, and then having a separate stable branch.
That being said, we do have a relatively stable release (the pre-beta branch), so I think it is probably a good time to sync over to master. Mike, are you interested in doing this?
Thanks,
deltacloud-devel@lists.fedorahosted.org