Re: API/ABI freeze?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: API/ABI freeze?
by sebas on Saturday 01/Dec/2007, @15:31

Ow, I might add the question:

Which changes are in your opinion needed to prevent those ugly workaround? Until now, for the release team, there's no visible reason to break BIC. Actually, no one has pointed out that there's a particular problem, why it would need a BIC exemption. So that's why I said that nothing's planned. Now if someone comes up with a good reason and explanation, we will seriously consider it, but until that does happen, we assume binary and source compatibility.

Related Links

·   Articles on KDE Official News
·   Also by sebas
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: API/ABI freeze?
by Anon on Saturday 01/Dec/2007, @15:38

Well, it's entirely possible that my info is out of date :) It's based on your original delay proposal on the Release Team mailing list.

See if you can find Oswald Buddenhagen (ossi), Thomas Braxton)(?) or Andrea Pakulat (apaku) and ask if there are any BIC KConfig updates that they still want to add. I think ereslibre and dfaure should know about the KJob stuff.

Hopefully, all this has gone in already and I'm worrying needlessly :)

[ Reply To This | View ]

Re: API/ABI freeze?
by sebas on Saturday 01/Dec/2007, @15:42

I'm aware of both of these, but it's not clear to me that those are really urgent. And neither David or Oswald did point out that this change is really a good idea to put in, they didn't make clear that it's both necessary changes or punished with 5 years of ugly workarounds.

I assume that all of the above people are aware that they should point it out. So yes, there were possible changes, and it has been brought up within the Release Team, but nobody came up with good reasons to break BIC (yet). If there are those issues, do contact the Release Team and ask for a BIC exemption, however.

[ Reply To This | View ]

Re: API/ABI freeze?
by Anon on Saturday 01/Dec/2007, @15:47

Ok, sounds like it's not as urgent as I feared - you can ignore this whole thread, after all ;)

[ Reply To This | View ]

Re: API/ABI freeze?
by Thomas Braxton on Saturday 01/Dec/2007, @19:46

AFAIK all the KConfig changes that have even been discussed are to non-exported classes, so there shouldn't be any BIC changes.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Ok, maybe my approach is over-engineered." -- Simon Hausmann
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.