Since our version numbers are a bit high in Bayonne2, I thought I would
comment about how things are versioned.
First, as I use C++, its rather easy to modify a class such a way that
it breaks binary compatibility with previous releases, either because
the object size has changed, or a new virtual has been inserted.
Generally, "abi" changes that break binary link compatibility with
previous versions are given a new major. Hence, this can be expected to
happen rather frequently, especially in early development.
Sometimes I will bump a version around a major functional
reorganization. Hence, what is different between 0.6 and 0.7 was in
part the seperated libexec. This I think is the sort of thing people
most often expect version changes for.
Given this, it would be mistaken to believe that versions represent
feature completeness, or can be used to estimate how many versions there
are until a 1.0 release of Bayonne 2. I would estimate that its current
completeness might be closer to where Bayonne was at 0.3-0.4, although
it is quite possible to have a very solid release of Bayonne2 by the end
of the year based on current progress.
begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
adr:;;;;;;USA
email;internet:[EMAIL PROTECTED]
x-mozilla-html:FALSE
url:http://www.gnutelephony.org
version:2.1
end:vcard
_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel
