Re: New Release?

> Thanks, will do. Since we changed the API in an incompatible way we have to
> increment the SO-Version of the library (and reset SO-AGE). We should
> therefore also increment some higher part of the version (instead of
> 0.8.x).
>
> What is your versioning policy? It looks to me that bugfix-only release
> have an incrementing micro version (0.8.1->0.8.2) and that API changes
> require the minor version to be incremented (so that the next release would
> be 0.9.0?).
>
> So the question is: Is 0.9.0 ok with you or do you have another proposal?

Generally I did:
micro = bugfix and very minor features.
minor = new features and source-incompatible API changes.

I don't mind which you chose, but API changes should have no influence on the 
version number unless it's source-incompatible.
-- 
Benoit Grégoire
Technologies Coeus inc.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Libofx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libofx-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHQbPqmZ6zzPlLuwMRArtMAJ9OYG1YAHzKXZp899aL+UYZ6gOjNQCgy5XM
O4ZcguEEGUU5yK8mVCHPGhc=
=rK3j
-----END PGP SIGNATURE-----