[Kde-scm-interest] Package splitting
mpyne at kde.org
Thu Jan 28 23:33:00 CET 2010
On Thursday 28 January 2010 01:56:38 Thiago Macieira wrote:
> Em Quinta-feira 28. Janeiro 2010, às 06.50.23, Chani escreveu:
> > > I think Thiago is on the spot that it's much safer to work on stable
> > > branch and forward-port bugfixes instead. Personally - there was very
> > > few of them - but it happened that I needed to reopen KDE bug marked as
> > > RESOLVED/FIXED just after fix has been commited to stable branch.
> > on back/forward-porting bugfixes... umm... is it *safe* to build and run
> > a 4.x branch after using trunk? kde config files have a reputation for
> > only letting you go forward, not back...
> That's orthogonal to any discussion on Git or how you make your patch land
> in both branches.
> The fact is you have to test your fix.
It's harder with Plasma since it changes frequently and you have way more
people working on it but with JuK I just leave my entire toolchain on trunk,
and switch only JuK to the stable branch when I test, since I know the KConfig
layout, cache layout, etc. hasn't changed. (Since I haven't changed it and no
one else works on it :(
- Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20100128/b28afd4f/attachment.sig
More information about the Kde-scm-interest