kdelibs/kmdi<-->kdevelop/lib/qextmdi

[Christoph Cullmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 26 January 2004 20:01, Alexander Dymo wrote:
> se kmdi from kdelibs but kmdi is not in a good
> condition and still is heavilly under development. That's why I'd like to
> keep our own (but similar to kdelibs HEAD version) - to allow BIC changes
> in kmdi and kdevelop mainwindow stuff. If we stick to kmdi from kde 3.2
> and impose 3.2 compatibility we won't be allowed to make changes
> in mainwindow and etc.
question is: will that help any maturing of kmdi if you always keep a copy 
around to avoid thinking about any BC interface that doesn't suck ? sure it 
is easy to have a local copy and fix any stuff like you want, but there was 
plenty of time to improve kmdi in kdelibs in a BIC manner + there is time to 
fix stuff in BC manner for kde 3.2.x releases.

cu
Christoph

- -- 
Christoph Cullmann
KDE Developer, kde.org Maintainance Team
http://www.babylon2k.de, cullmann at kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAFYjJyPjDGePm9UIRAqvVAJ9BfT5bNd+pr6or+6LxAL8dj1xPmwCfclWL
tuC7yEsRT6/CYdK1pQbLIBQ=
=OCpx
-----END PGP SIGNATURE-----