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

List:       kde-core-devel
Subject:    Re: Git Feature Branch Naming Policy
From:       Torgny Nyblom <kde () nyblom ! org>
Date:       2011-04-26 16:37:47
Message-ID: 2197120.Co8A79sJlA () explosive ! nyblom ! org
[Download RAW message or body]

On Tuesday 26 April 2011 15.52.18 John Layt wrote:
> Hi,
> 
> Did anything come out from discussions on feature branch naming in git? 
> With GSoC starting soon we'll be getting a lot of new feature branches and
> it would be nice if they were consistantly named to make them easy to find
> and manage.
> 
> See
> http://community.kde.org/20110213_GitWorkflowAgenda#How_To_Handle_Topic_Bran
> ches for the original meeting notes.
> 
> I'd prefer to see the gsoc branches under a common prefix in the main
> project repo rather than as personal branches or repos:
> 
>   origin/gsoc2011/<subproject>/<branchname>

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?

/Regards
Torgny
[prev in list] [next in list] [prev in thread] [next in thread]