Git Feature Branch Naming Policy
johnlayt at googlemail.com
Tue Apr 26 18:59:45 BST 2011
On Tuesday 26 Apr 2011 17:37:47 Torgny Nyblom wrote:
> Why this long name with multiple namespaces, the branches should be deleted
> once merged so we won't have a collection of old soc branches around for
Well it's based on the original naming proposal to try keep things a little
organised, especially for repos with multiple apps or libraries in them. As
mentioned, single app/library repos won't need the subproject level. We want
to add the gsoc in the name somewhere to make them easy to find, but putting
it after the subproject seemed a bit less easy to group them.
Yes, the idea would be to prune branches once they are merged, or have a
regular manual garbage collection as described in the link I gave, but reality
is that GSoC projects can take an extra release cycle or two to get polished
befor ethey are ready to be merged so it's better to be tidy from the start.
Besides, that's just the remote name, there's nothing stopping you from having
a shorter name locally to make life easier.
More information about the kde-core-devel