[EMAIL PROTECTED] (Linas Vepstas) writes:

> On Fri, Jul 09, 2004 at 06:15:35PM +0200, Andreas Rottmann was heard to remark:
>> [EMAIL PROTECTED] (Linas Vepstas) writes:
>> 
>> > Whenever an api changes in an incompatible manner, please bump the 
>> > major version number. That's what major version numbers are for.
>> >
>> Sorry, but there is no "standard scheme" for version numbers everyone
>> must adhere to. 
>
> Actually, for libraries, there is ...  incorrect version leads to
> linkage breaks.  Its actualy a technical problem, and not a matter
> of taste or opinion.
>
This is for library SONAMES, but that was not what I was talking about.

>> I prefer to use minor version number as "branch
>> indicator" (like the Linux kernel, GNOME, ...). Branches may break
>
> There is considerably more freedom of interpretation when dealing
> with an application.  Applications don't have API's that migh break
> backwards compat; you can choose version numbers that make good 
> slogans ("win95").
>
> But Gnome is not the example you think: [...]
>
> Note that the Linux kernel is also a bad example: [...]
>
OK, but I think as long as you are consistent, it's IMHO no problem to
break API on minor version numbers :-p

Andy
-- 
Andreas Rottmann         | [EMAIL PROTECTED]      | [EMAIL PROTECTED] | [EMAIL 
PROTECTED]
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

It's *GNU*/Linux dammit!
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to