--===============1267874295==
Content-Type: multipart/signed;
	boundary="nextPart5241293.3P81raVWUX";
	 protocol="application/pgp-signature";
	 micalg=pgp-sha1


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

On Thursday 13 December 2007 18:43:53 Mauricio Piacentini wrote:
> > i'd sooner see us (loosely) sync along with the Qt dev cycle (which has
> > become much more regular, ~9 month per release) to keep a steady flow
> > of feature / bug fixes going between KDE and Qt.
>
> Ok, keeping a pace with Qt actually makes more sense than any other
> (arbitrary by nature) decision. Also, with 4.0 out, we will resume the
> cycle of new applications going to playground or maybe kdeapps, and then
> =A0 waiting to be picked for inclusion in the main releases or extragear.

Sounds sane.

> This is something we should consider maybe, with feedback from TT.

Not sure what you want feedback on :)
But I'm positive that having a KDE release slightly after a Qt release is=20
something that nobody will have a problem with here at TT :)
=2D-=20
Thomas Zander

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

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

iD8DBQBHYXoLCojCW6H2z/QRAr/rAJ9NTSQ1rXLnCkrTrxntlqnW7WT1RACg2o6Y
XiSLeMORMeWKgrTAD/mgneE=
=IyCG
-----END PGP SIGNATURE-----

--nextPart5241293.3P81raVWUX--

--===============1267874295==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

--===============1267874295==--