On Wednesday 12 March 2014 14:46:08 Sascha Peilicke wrote: > On Wednesday 12 March 2014 08:36:03 christopher_dearb...@dell.com wrote: > > Hey guys, > > > > Unless there is a compelling reason for doing this (and I haven't heard > > one), I would propose that we leave everything as-is. I don't see a need > > for doing this. > > I guess there are two aspects to it: > > New people are confused by either going crowbar 2.x or 1.x, which means > either using Dell's primary area of innovation or SUSE's. Despite the > advent of opencrowbar, this is still very confusing to people. Nothing to > be solved easily. > > On the other hand, seasoned developers with an eye for beauty are > consistently annoyed by the continued over-use of Github. Err, I meant "branches".
> People use the > "crowbar" Github organization for their private feature-fiddling while they > should do that in their own fork. Whether to keep stable-release branches > or use tags instead is a matter of taste, I believe. But the following > examples are really a miss- use: > > remotes/crowbar/release/hadoop-2.1/master > remotes/crowbar/release/hadoop-2.2/master > remotes/crowbar/release/hadoop-2.3/master > remotes/crowbar/release/hadoop-2.4/master > > It should be one "hadoop" branches with tags 2.1, 2.2, 2.3 and 2.4. > > remotes/crowbar/release/mesa-1.6.1/master > remotes/crowbar/release/mesa-1.6/master > remotes/crowbar/release/mesa-1.7/master > > Same here. > > remotes/crowbar/release/mesa-1.6.1/openstack-build/master > > WTF? Away with thee! > > I guess that's where the most cleanup potential lies. Lastly, we had discussed branch naming. Just to clarify again, the branch names "release/foo/master" and "release/bar/master" share ~90% redundancy without transporting any additional information. On the other hand, the following convention is crystal-clear: master stable/foo stable/bar But in our case, it's likely not that simple. Github repos under the "crowbar" org have several "master" branches in reality. While I am not fully aware of which parts of Dell's activity take place under opencrowbar these days, we likely can't get around acknowledging this. On the other hand, the branch naming worked good enough for at least the core contributors so far. -- Viele Grüße, Sascha Peilicke _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
