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

List:       kde-core-devel
Subject:    Re: Moving 3.5 development into branches/KDE/3.5
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2005-05-31 6:51:06
Message-ID: 200505310051.11175.aseigo () kde ! org
[Download RAW message or body]


On Tuesday 31 May 2005 12:34, Stephan Kulow wrote:
> into trunk later. But that doesn't work for kicker. We really need a

which is why i'm trying to hurry up on the 3.5 stuff, mostly by just saying 
"no more features" and moving to clean up items, of which there are but a 
handful at this point. i've put a call out for feature adds on panel-devel 
with a note that if nobody comes up with anything compelling that the feature 
freeze for kicker will be next monday, with a week or two of bug fixing and 
Q&A. so it may even be before the end of June, but no promises ;)

> We really need a gradually ported
> gradually ported KDE4 to test changes done to the framework. And we have to
> make sure we're not loosing overview - and if all KDE 3.5 development is
> going to be merged by me, we're going to loose overview. So I want a change
> in policy who is responsible for merging KDE 3.5 development into the then
> main development branch - I don't want to dictate a policy on when this
> needs to be done and not even how.

that all makes 100% sense IMHO =)

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

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

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