Hi,
"Here are a set of rules to help you update your library version
information: [...]
3. If the library source code has changed at all since the last
update, then increment revision (c:r:a becomes c:r+1:a).
4. If any interfaces have been added, removed, or changed since the
last update, increment current, and set revision to 0.
5. If any interfaces have been added since the last public release,
then increment age.
6. If any interfaces have been removed since the last public release,
then set age to 0."
each rule should be applied if the condition is matched.
I.e. 2:0:1 -> 2:1:1 -> 3:0:1 -> 3:0:2. So 3:0:2 will be the library
version for the next release.
Some simpler examples we might encounter frequently:
Bugfix release: c:r+1:a
Enhancement release (API fully compatible with older releases): c+1:0:a+1
API change in an incompatible way: c+1:0:0
Marcel Holtmann wrote:
I think we are ready. Christian, how should the library version be
changed for our next release.
cu,
Christian
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Openobex-users mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/openobex-users
