KIO::NetAccess static methods question

Andras Mantia amantia at kde.org
Wed Oct 24 22:27:05 BST 2007


On Thursday 25 October 2007, Andreas Pakulat wrote:
> On 24.10.07 22:22:49, Leo Savernik wrote:
> > c) release 4.0, admit that it didn't cut it, and release 5.0 in
> > place of 4.1 to make KDE shine.
>
> Just one comment: How is 5.0 with BIC changes different from 4.1 with
> BIC changes? 

Third party developers must be sure that if they write something now, it 
will work with the rest of 4.x releases. Doing a 5.0 instead of 4.1 (if 
4.1 breaks BC) would make KDE a serious BC keeping project (unlike some 
famous other projects). This is the theory. The truth is that aside 
being BC, the other important issue is how long a version lives on. If 
an 5.0 with different API is released quickly after 4.0, that would 
also piss off third party developers. Still IF there will be a BIC 
kdelibs[*] in 4.1, I'd vote for not calling it 4.1 anymore, for the 
reasons Leo said.

> 4.1, I doubt you can run the simple Qt4.3 examples against a Qt4.0
> (but I'm not sure).

You got it wrong. The idea of BC is to have Qt4.0 examples running under 
4.3 without recompiling. The other way around it is normal that it 
won't work.

Andras

[*] As it is known Plasma will break BC. Luckily plasma isn't in 
kdelibs, so this exception might be acceptable.

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071025/51654c26/attachment.sig>


More information about the kde-core-devel mailing list