Hi, proposal ... please be patient, I'm not SCM guru ;)
We have two HG repos .... one is 'devel; and the second is 'stable' Now we are committing into 'devel' especially into kde-4.1.4 branch .... it is good ... but !!! I think some of those commits should go into default branch too, because they are touching FOSS* bits ... so my proposals in this point are ... 1. merge branches together, kde-4.1.4 will be master in that merge. 2. synchro 'devel' and 'stable' At this time stable has 4.1.4 branch and devel has 4.1.4 branch and continue .... into 'stable' should go every bit around KDE4 4.1.4 and particular FOSS bits into 'devel' should go everything _NEW_ (KDE 4.2, new version of FOSS etc ...) If someone will make a commit into 'stable' around FOSS bits, then he should make this commit into devel too (if is reasonable, of course). Any comments, proposals ? P.S. ... cvsdude svn repo should continue hold the source trees and build infrastructures. ;) -- Lukas 'Luc' Oboril IRC nickname: luc^ at freenode When dealing with people, let us remember we are not dealing with creatures of logic. We are dealing with creatures of emotions, creatures bristling with prejudices and motivated by pride and vanity. Dale Carnegie
