[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Git Feature Branch Naming Policy
From:       Shaun Reich <predator106 () gmail ! com>
Date:       2011-04-26 17:53:09
Message-ID: BANLkTinP8x5AXFV2r-DscCVfzkMjfJRvVA () mail ! gmail ! com
[Download RAW message or body]

>> I'd prefer to see the gsoc branches under a common prefix in the main
>> project repo rather than as personal branches or repos:

I think that's a good idea too, especially given (below).

>>
>>   origin/gsoc2011/<subproject>/<branchname>

Probably don't need subproject, since the branch name will
probably/should tell you all you need to know.

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

Ideally, yes. But as for the branches themselves being merged, or even
in a timely matter, that's a different story, as I'm sure there are
many situations...like the project only being half done and the
gsoc'er leaving (sadly), etc.. It even has other benefits, like "where
do I go to look at the code for ___ project?", and it's all right
there. As opposed to a personal clone under somebody's name. Note we
had a similar situation in svn, except it was less namespaced and more
ugly


-- 
Shaun Reich,
KDE Software Developer (kde.org)

[prev in list] [next in list] [prev in thread] [next in thread]