DevHeads.net

Adding experimental parts to a KF5 library

Hi,

Because of the short release cycle for the frameworks, it is hard to
have bigger new features included into one of them. Slowly evolving
APIs while developing stuff leaves a lot of crud and deprecated
methods later.

What is our policy about having experimental (unstable API/ABI) parts
in a framework (obviously, in a separate binary, so that the main
library remains BC)?

Cheerio,
Ivan

Comments

Re: Adding experimental parts to a KF5 library

By Mark at 01/09/2015 - 15:54

Or Qt as another example, they simply say it's a "technology preview" :)
I don't think they put it under a special namespace.