Hello!
Henry Gebhardt has written on Wednesday, 24 September, at 20:32:
>On Wed, Sep 24, 2014 at 02:24:28PM +0300, Andrej N. Gritsenko wrote:
>> Henry Gebhardt has written on Tuesday, 23 September, at 23:15:
>>> Two minor things: a) To avoid confusion, I would start with the ABI_VERSION
>>> equal to the current release number, e.g. 0.8.0. We can always let them
>>> diverge later.
>> In general, soname numbers are not (and never should be) relevant to the
>> software release - those numbers are just compatibility numbers, and for
>> first non-alpha release of library ABI version should be 1, with age and
>> revision at 0. But while the 0.8.0 will be in development (alpha, 0.7.99
>> or whatever), it would stay at 0.0.0. :)
>Not sure I agree. Yes, they are only compatibility numbers, but we want
>to minimize confusion. We are treating the 0.x.y releases as almost
>stable already. And although it doesn't really matter, starting with
>0.8.0 as the first ABI version would let everyone know since when this
>library exists. No need to read any documentation. We can leave it at
>0.8.y for as many releases as we want to.
It's not how it works. I understand your intentions but unfortunately
dynamic library loader wouldn't agree with you. The first release of the
library should come as 0.0.0, then after any added API second number have
to be increased, and on any change or deletion of some API first number
should be increased and others reset to 0. Look - libmenu-cache is 0.7.0
but soname has 3.0.4 already, and soon it will be 3.1.0 since I need to
add few new APIs to it.
Since our API now is different from very first one, I believe that it
buy us a right to start not from 0:0:0 as libtool documentation suggests
(https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html)
but from 1:0:0. Believe me or not but that is a right way - to set 1.0.0
when we release it the first time, i.e. in lxpanel-0.8.0. Don't be afraid
of such number, please. :)
>Thank you,
>Henry
With best regards,
Andriy.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
