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

Hi!

As originally announced I would like to have trunk based on Qt4 really soon=
=20
now. For this I would like to branch off trunk this friday (and use the tim=
e=20
till then to do an initial port of some more modules).

The translations were unaffected and would happen from the 3.5 branch. The =
3.5=20
branch would still be an active development branch, but every change done=20
there has to be done also in trunk. The actual schedule on merging might va=
ry=20
from app to app or even module to module, but that should be the goal. We c=
an=20
even make a public list of all revisions happened to 3.5 branch and strike=
=20
off forward ports through a commit keyword (or some similiar mechanism).

But I think this needs to be done even before Qt4 is released. And it's no=
=20
longer a completly uncertain adventure, but we know pretty well by now how=
=20
much porting effort is behind Qt4 - but what we do not know is how well it=
=20
runs. Getting konqueror to compile was done in pretty short time, but getti=
ng
it to work for daily usage will still take a good while and we should as=20
project should have good overview over it.

Everyone is free to stay and develop for KDE 3.5 as long as he feels like i=
t,=20
but everyone should be aware that the development for it needs to be ported
to KDE4 without too much major pain or you're just asking for frustration.

If no objections are raised on kde-core-devel, I will announce my plans to=
=20
kde-cvs-announce.

Greetings, Stephan

--nextPart2556491.FGfYgnVmh7
Content-Type: application/pgp-signature

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

iD8DBQBCmxXswFSBhlBjoJYRApuoAJ9UyKilsnGA7YIvu21QLKbPYwshQQCePc2i
OxwZwYvgJH0CY431qde/xPE=
=CRYd
-----END PGP SIGNATURE-----

--nextPart2556491.FGfYgnVmh7--