--nextPart7296353.cPzJjZLTA1
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Charles Samuels wrote:
>I'm concerned that kdelibs will change a lot, leaving applications with
> a moving target to develop against.  I would like to see kdelibs
> stabilized somewhat before we start developing against it outright.
>
>Currently kdelibs doesn't change very much, which makes things very
> pleasant to develop against for both us and our 3rd party developers.

I believe this is what Coolo meant when he said kdelibs HEAD=20
(/trunk/kdelibs) would be Qt4, while other modules would be Qt3.

In other words:
=2D /trunk/kdelibs goes Qt4
=2D /trunk/everything_else still Qt3/kdelibs-3.4
=2D We'd have a branch for people working on porting non-kdelibs for=20
Qt4/kdelibs4
=2D when /trunk/kdelibs stabilises enough, we'll start moving other modules=
=20
to Qt4, merging the branches
at that point in time, kdelibs4 should be less moving a target.

I'm not saying kdelibs4 should feature-freeze or fix its binary=20
compatibility too early. I'm just saying that it should get a chance to=20
stabilise first.

=2D-=20
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

5. Swa he g=C3=A9anhwearf t=C3=B3 timbran, and hwonne he c=C3=B3m, l=C3=A1!=
 Unix cw=C3=A6=C3=B0 "Hello,=20
World". =C7=BCfre =C7=BDghwilc w=C3=A6s gl=C3=A6d and seo woruld w=C3=A6s f=
r=C3=A9o.

--nextPart7296353.cPzJjZLTA1
Content-Type: application/pgp-signature

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

iD8DBQBCEVtwM/XwBW70U1gRAn+8AJsGbB7pp4YNTUUchQWUUDjiIYQGuACguc8u
/8Z7uBn1+P6osS3wNo67b5Y=
=MW1r
-----END PGP SIGNATURE-----

--nextPart7296353.cPzJjZLTA1--