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

List:       kde-core-devel
Subject:    Git Feature Branch Naming Policy
From:       John Layt <johnlayt () googlemail ! com>
Date:       2011-04-26 14:52:18
Message-ID: 201104261552.18749.johnlayt () googlemail ! com
[Download RAW message or body]

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_Branches 
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>

e.g. in kdelibs.git have "origin/gsoc2011/kdecore/astronomical-calendars"

Cheers!

John.
[prev in list] [next in list] [prev in thread] [next in thread]