[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-extra-gear
Subject:    Re: [Kde-extra-gear] Rethinking position on trunk x branches
From:       Angelo Naselli <anaselli () linux ! it>
Date:       2007-03-10 10:23:34
Message-ID: 200703101123.34841.anaselli () linux ! it
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Alle 15:11, giovedì 8 marzo 2007, Helio Chissini de Castro ha scritto:
> Em Qui 08 Mar 2007, Angelo Naselli escreveu:
> > As asked, I'm back on this subject following the old thread.
> > As far as I'm concerned I don't mind to branch keg either for kde4
> > or for kde3 svn should be easy to use to manage for that.
> > But I believe the way to is to branch all the keg.
> 
> Right, fully agree
> 
> > If someone cannot work on kde4 yet can disable his/her application
> > to be built. AFAIK kde-i18n is breanching (or has already) so why
> > not following their example? If they've chosen to stay in trunk for
> > stable we can do that either.
> 
> Agree too, but my preference is kde4 in trunk and branch all kde3
> 
> I have some proposition that give us time to prepare, which is set the day of 
> branching exactly the day of kdelibs 4 API freeze. As current state of 
> people's work, it's near, right ?
> 
> Otherwise, we can set branch for soon as next weekend.
Well we haven't planned any starting date yet, so, when it's the same for me. 
But sure sooner or later all of us has to do that... 

> > As I told you in mine first, It seems silly to me branching every
> > single keg application.
> 
> True, and branch all keg it is.

So can someone with the "power" take a decision? Or do we have to wake 
up a day when keg won't compile anymore? :)

Angelo

[Attachment #5 (application/pgp-signature)]

_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@kde.org
https://mail.kde.org/mailman/listinfo/kde-extra-gear


[prev in list] [next in list] [prev in thread] [next in thread]