From kde-core-devel  Wed Jul 30 10:12:48 2003
From: Ralf Nolden <nolden () kde ! org>
Date: Wed, 30 Jul 2003 10:12:48 +0000
To: kde-core-devel
Subject: Re: Drafting a policy? [was: Re: Qt 3.2 requirement]
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105956004416783
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-02=_ho5J/Jk2Pq6+WLa"


--Boundary-02=_ho5J/Jk2Pq6+WLa
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Mittwoch, 30. Juli 2003 11:49, Stephan Kulow wrote:
> On Wednesday 30 July 2003 09:08, Ralf Nolden wrote:
> > BTW: why do we have a release coordinator to decide about such things ?
> > Stephan ? :-)
>
> I already expressed in another mail, but to repeat it explicitly: so far
> I don't see a reason to jump on a 3.2 requirement as it doesn't give
> us any features we can't live without. But I suggest for the betas we'll
> require 3.2 to limit the testing space.

Ok, now we only need to know the bugs that KDE 3.1.x shows when running wit=
h=20
Qt 3.2 like Waldo suggested and we *finally* have a roadmap that one can=20
orientate on :-)

I would like to keep track of the branch's requirements so Chris Cheney and=
=20
the other debian maintainers know what to expect and I can schedule with=20
Martin when to switch to Qt 3.2 in unstable as soon as the build requiremen=
t=20
for the branch has < Qt 3.2 dropped.

Ralf
>
> Greetings, Stephan

=2D-=20
We're not a company, we just produce better code at less costs.
=2D-------------------------------------------------------------------
Ralf Nolden
nolden@kde.org

The K Desktop Environment       The KDevelop Project
http://www.kde.org              http://www.kdevelop.org

--Boundary-02=_ho5J/Jk2Pq6+WLa
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA/J5ohu0nKi+w1Ky8RAl6FAKCmNhmLBYL1IhFp6UAgnCjl5EQppgCbBbrT
lv4DITjKGgrDFUN8ZSuiAkY=
=YTse
-----END PGP SIGNATURE-----

--Boundary-02=_ho5J/Jk2Pq6+WLa--