--===============1871750989==
Content-Type: multipart/signed;
  boundary="nextPart1897887.6aVruHYbvP";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

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

Hi all

I'm right now not sure what to do with the kdenetwork module... Not all app=
s=20
are working very well atm. Matt Rogers (mattr) thinks that Kopete will not =
be=20
ready for 4.0. KRDC is also not ready so far. Probably I will get it done f=
or=20
4.0. I don't know yet.

Apps that will be ready for sure are only Krfb and KGet. Filesharing and=20
lanbrowsing: I have not tested them yet. Laurent Montel worked on them and=
=20
thinks that they will be ready. Kppp seems to work, but I have no posibilty=
=20
to test it.

I will drop the remaining apps (Kpf, KWifiManger, KDict) the next monday as=
 I=20
have written already a mail to this list.

What do you think? Should we release kdenetwork 4.0 and just disable the ap=
ps=20
that are not ready in the release? (Of course, we are not going to release=
=20
not working apps...) Or should we not release kdenetwork at all?

Bye
urs

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

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

iD8DBQBGYDHmooBDqI2Jn8gRAv2uAJsHBweyJSYRTajXUVEfcIOmZmwXvwCgmMu5
ZsPoi/B8TfTsLYBApTbad2s=
=RzDE
-----END PGP SIGNATURE-----

--nextPart1897887.6aVruHYbvP--

--===============1871750989==
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

--===============1871750989==--