From kde-core-devel  Sun Aug 30 22:56:06 2009
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Sun, 30 Aug 2009 22:56:06 +0000
To: kde-core-devel
Subject: Re: KDE Trunk based on Qt 4.6
Message-Id: <200908301656.06756.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=125167302412757
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1468209.N99CvWQnW7"

--nextPart1468209.N99CvWQnW7
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On August 30, 2009, Albert Astals Cid wrote:
> So if we do what distros do why the hell do we even have a schedule?

it's not a great situation, no. but while we work on improving it (and some=
=20
people are trying to :) we also have the reality that our users will be usi=
ng=20
KDE 4.4 with 4.6

> And now more seriously if there are problems running KDE 4.4 with Qt4.6
> that means either:
>  a) There's a bug in KDE 4.4 that we have to fix
>  b) There's a bug in Qt 4.6 Nokia has to fix
> This has nothing to do with depending or not on Qt 4.6

if we depend on it, then:

* we know all our users will be using the same combination of KDE and Qt=20
libraries; this makes troubleshooting easier

* we know that our developers will be working with that combination prior t=
o=20
release, meaning we will catch bugs before release. proactive bug squashing=
 is=20
good.

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

KDE core developer sponsored by Qt Software

--nextPart1468209.N99CvWQnW7
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkqbA4YACgkQ1rcusafx20N/EwCfa0m0gNII36/duTzx/LWA7pZn
kaEAn1J8rCKulclGj1861j7m4R+beIst
=QhaS
-----END PGP SIGNATURE-----

--nextPart1468209.N99CvWQnW7--