From kde-core-devel  Wed Jun 01 01:36:22 2005
From: Benjamin Meyer <ben () meyerhome ! net>
Date: Wed, 01 Jun 2005 01:36:22 +0000
To: kde-core-devel
Subject: Re: Moving 3.5 development into branches/KDE/3.5
Message-Id: <200505312136.25993.ben () meyerhome ! net>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=111758952906398
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1228404.y6f2SdWSlD"

--nextPart1228404.y6f2SdWSlD
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 31 May 2005 8:17 am, Benjamin Reed wrote:
> On 5/31/05, Brad Hards <bradh@frogmouth.net> wrote:
> > 0. Only port kdelibs to Qt4 at this stage
> > 1. Do the application porting as an experiment/testcase only - a few
> > tricky apps from kdebase, a couple of little ones, a couple of bigger
> > ones. Don't try for a complete, stable port.
> > 2. Spend the time between now and the 3.5 freeze on kdelibs polishing -
> > can we get 100% code coverage in tests? could we valgrind kdelibs (test=
s)
> > completely clean? Could we document it better?
>
> This would also give us time to work on the new build system; right
> now I'm anxious to start working on KDE4 for Qt/Mac, but the current
> autotools stuff *sucks* for doing Qt/Mac work (for various reasons).

Speaking of which the previous thread on the build system kinda tottered ou=
t. =20
Has anyone else had a chance to play around with all of the different tools=
=20
mentioned to provide more feedback on the topic?

=2DBenjamin Meyer

=2D-=20
aka icefox
Public Key: http://www.icefox.net/public_key.asc

--nextPart1228404.y6f2SdWSlD
Content-Type: application/pgp-signature

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

iD8DBQBCnREZ1rZ3LTw38vIRAuq8AKC2kFK1eqF8niYWhqVr6yotYuHbbwCfXjdG
W6Uh3bMUqonicvwuzTEeEk8=
=V/Yp
-----END PGP SIGNATURE-----

--nextPart1228404.y6f2SdWSlD--