Work Branches

Valorie Zimmerman valorie.zimmerman at
Sun Oct 6 06:45:00 BST 2019

Hey Ben and developers,

On Fri, Oct 4, 2019 at 7:11 PM Ben Cooksley <bcooksley at> wrote:

> Hi all,
> Recently we had a discussion (which I think may have ended up spread
> over a couple of mailing lists in the end) concerning branches and the
> ability to force push to them.
> Current policy forbids force pushing to branches except in very
> limited circumstances (essentially where it is the only option to fix
> a branch)
> The discussion ended with two ways forward, but no 100% clear
> consensus on which way we want to go forward. The two proposed ways
> were:
> 1) Only protect 'master' and declared 'stable' branches.
> 2) Protect all branches, aside from a given prefix (proposed to be work/)
> I'd like to clean this up and sort out the policy we want to have
> surrounding this so we can move forward.
> From my perspective i'd rather we go with Option 2, as this will be
> the approach that will be easier to both implement and maintain in the
> long term and be the least likely to cause collaboration problems (as
> the branch naming conventions will be universal across all our
> repositories).
> Thoughts?
> Thanks,
> Ben Cooksley
> KDE Sysadmin

We in the CWG have been in discussions about this too, since there have
been some people trying to force-push even after being warned by the system
and sysadmin. I see that there seems to be consensus about proposal 2.

My question is how will this be documented and then how do we spread the
word? Our devel announce list does not seem to be as well-read as it should

Perhaps the new policy can be linked to the Manifesto or even added to it?


-- - pronouns: she/her
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the kde-core-devel mailing list