[Silgraphite-devel] API Changes

[Martin H. <mar...@si...>]

Dear All,

The next version of the graphite engine (1.2.0) will have some new API functions added and some deprecated. As a result we need to increase the interface number and we can also increase the age (since we aren't changing or deleting any functions). Thus we are going from 2.0.0 to 3.0.1 (this is separate from the release numbering scheme). I.e. we will be binary backwardly compatible with the existing API. Is there anything we should be doing to reduce the impact on packagers and application integrators as we do this? Feel free to pull the code and take a look (hg clone http://hg.palaso.org/graphitedev).

As you can see we are working to keep API changes to a minimum and to minimise the impact of those changes. So we hope we don't have to do this very often.

Yours,
Martin