Hi,
I would like to try wherever possible to only extend the API and not
change or remove existing methods. This will help to ensure, that
plugins written for 2.0 will stay working for minor releases.
If there is a (more clever/better) replacement for a method, the old
one should be
Hey all,
Now that we have 2.0 out does that mean we are maintaining a stable API? I
have a fix for a bug in the composer export which requires an API to public
facing APIs, changing int to QString.
What is the procedure now. Do we add overloads for something like this and
depreciate the old