Changes to branch management
Albert Astals Cid
aacid at kde.org
Fri Dec 26 11:42:15 GMT 2014
El Dijous, 25 de desembre de 2014, a les 20:29:12, Thomas Friedrichsmeier va
> On Thu, 25 Dec 2014 20:21:05 +1300
> Ben Cooksley <bcooksley at kde.org> wrote:
> > > 1) Everybody can create, delete and force-push to all branches
> > > except the "reserved" ones (kde/*, master, stable,... see the list).
> > >
> > > 2) People are free to create, delete and force-push to all branches
> > > below my/$username/ (in my case, tat would be my/jkt/foo for
> > > example). Only repo owners can create, delete and force-push to
> > > arbitrary branch names.
> > Agreed. Can we have a show of hands / etc as to which one would suit
> > people best?
> > I will add a 3rd possibility though.
> > 3) People are free to create and delete to all branches below work/*.
> > Creation and deletion of branches outside this would be limited to
> > project admins (release managers). It also allows other developers to
> > cleanup as needed so it doesn't all fall on the repository admin /
> > sysadmin.
> > This removes developer usernames from the branch names - which is
> > probably better for long term collaborative branches (which i've seen
> > used in a number of projects) and doesn't make a difference for short
> > term branches.
> I like 3 best.
> This seems like a very straight-forward solution that offers the current
> level of protection for all existing branches, while allowing a lot of
> flexibility in managing non-protected branches (including, importantly,
> the possibility to organize by feature / purpose rather than by
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel