On Saturday, January 31, 2015 22:52:22 Andreas Pakulat wrote: > Hi, > > just a short note (don't want this to become a complete subthread > distracting from the actual proposal-discussion) > > On Sat, Jan 31, 2015 at 9:38 PM, Alexander Neundorf <neund...@kde.org> > > wrote: > > that KDE still couldn't agree even on a set of git workflows to use, the > > > > wiki page still just lists a few proposed drafts. :-/ > > I think thats actually a good thing and would just not work for 'KDE' (i.e. > the whole community with all projects). KDE is just to big and diverse to > impose one particular git workflow onto all its projects, in particular > since some of them also impose certain release management. Different > projects move at different paces, they have different needs for their > release management and the maintainers actually doing the work may have > differing opinions or even just time.
Even if it should not be possible to agree on ONE workflow, maybe it should be possible to agree on two or three (e.g. everything in master, or everything in feature branches, and maybe a third one) standard workflows, and document them properly. Then every project could simply state "we are using workflow (A|B| C)" and things would be clear. It wouldn't be too much IMO to make it mandatory for "KDE" projects to use one of two/three official KDE git workflows. Alex
