From kde-core-devel  Tue May 31 06:51:06 2005
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Tue, 31 May 2005 06:51:06 +0000
To: kde-core-devel
Subject: Re: Moving 3.5 development into branches/KDE/3.5
Message-Id: <200505310051.11175.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=111752235005946
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1312526.zNSAvln8tk"

--nextPart1312526.zNSAvln8tk
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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=
=20
"no more features" and moving to clean up items, of which there are but a=20
handful at this point. i've put a call out for feature adds on panel-devel=
=20
with a note that if nobody comes up with anything compelling that the featu=
re=20
freeze for kicker will be next monday, with a week or two of bug fixing and=
=20
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 chan=
ge
> 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 =3D)

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

--nextPart1312526.zNSAvln8tk
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCnAlf1rcusafx20MRAoGuAJ4khiFcRJdNHG3yTYQWGXwgF4e6EACeN7nm
MZKW6r+rl08p0e8ilOs2mBk=
=44QE
-----END PGP SIGNATURE-----

--nextPart1312526.zNSAvln8tk--