Proposal for branching policy towards KF5

[Sebastian Kügler]

On Thursday, July 18, 2013 10:42:35 Martin Graesslin wrote:
> On Thursday 18 July 2013 10:26:06 Sebastian Kügler wrote:
> > - master stays on 4.11, receives bugfixes, our releases are based on this
> > 
> >   branch and their version number will stay 4.11
> 
> how do we prevent that people commit features into master? I would prefer if
> we lock down master in gitolite so that only module admins can commit to
> it. This would mean that bugfixes needs to be done in the branch?

We discussed that during lunch (including Martin, so just catching up the list 
here):

Blocking commits into master would create a situation very similar to kdelibs 
previous setup. A solution we came up with, and which received a lot of "Hm, 
that sounds like a good idea" is to block commits into master that do not have 
a REVIEW: line in them, so we make sure that patches go through reviewboard. 
This way we "encourage" good behaviour.

Cheers,
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9