RFC: develop feature branches in main repo

[Leo Franchi]

On 9 Nov 2010, at 16:25, Bart Cerneels wrote:

> On Tue, Nov 9, 2010 at 16:50, Ian Monroe <ian at monroe.nu> wrote:
>> I know some people are still using Gitorious repos and such for the
>> ongoing work. However recently everyone has been granted the right to
>> create branches on our git.kde.org/amarok.git repo.
>> 
>> I think it would raise the visibility of feature branches if everyone
>> just pushed them to the main repo. This would make things a bit
>> 'messy', but I don't really think its a big problem. We could have a
>> spring cleaning and move all the old branches into amarok-history if
>> it becomes an issue.
>> 
>> I do suggest that branches be named YYYYMMDD-description.
>> 
>> Ian
> 
> Regardless of name (which is to trivial to keep discussing) I suggest
> to require the creation/push of a new branch is announced on this
> mailing list. This keeps a log in a public archive with the reason for
> the branch, a place to discuss and to get more contributors.


Makes sense to me. We shouldn't have such a huge number of branches that they clog up the mailing list anyway.
---
Leo Franchi				(512) 775 5637

lfranchi at kde.org
leo at kdab.com