[Dar-libdar_api] Time to freeze the API

[Denis C. <dar...@fr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

There is now quite one year that took place the last major release,
since that time a lot of new features took place in the development
version. Some more have to come yet, but it is time to make theses
already implemented become a bit more public, so we are now on the way
to the next major release: version 2.3.0. / API 4.0.0

For today The API is frozen, so you have several weeks to report
problems in its design, things I could have missed as my point of view
is not really the one of a full user of the API like kdar is. The API
Tutorial is almost up to date, some arguments are missing in regards to
the two latest features used, but doxygen should bring you all
information needed.

I let you refer to the "Changes" file in CVS trunk, to see the list of
new features and their impacts on the API. If something is not clear and
not enough detailed don't hesitate to send an email to the libdar-API
mailing-list.

In the meanwhile I have a big work to do with documentation, depending
on my free time, I hope to finish before end of January. Then would come
the traditional one-month-pre-release phase that would end up with the
2.3.0 release.

Thanks to all for your patience, feedback, suggestions and encouragements.

Cheers,
Denis.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFDlIEXpC5CI8gYGlIRAgW5AJ4nz1IvJs+uGBG6TvSJ9Xy2yLp1lACfZZxT
/+g9snMHXuV23TKCdMrIGuc=
=00bI
-----END PGP SIGNATURE-----