[Development] Proposal: New branch model

Sune Vuorela nospam at vuorela.dk
Sun Feb 10 09:44:12 CET 2019

On 2019-01-25, Lars Knoll <lars.knoll at qt.io> wrote:
> * I think it makes the life of casual/new contributors easier. Simply always
>   develop and push against the development branch. The more experienced
>   reviewer can then easily decide that the fix should be cherry-picked into a stable branch.

I'm mostly a casual contributor, mostly dealing with fixes to bugs found
in specific releases. I'm doing my fixes in those releases. Because
that's where I need them. If I could just then push it and more or less
forget about it, that's the thing that would make it easier.

This seems to me that I need to move the fix forward to dev, then push
it, then backport it. I might not even have a dev build handy. Because
I'm basing my work on top of something released.

 - independent contractor, KDE Developer and Debian Developer

More information about the Development mailing list