Re: ABI compatibility between rtt-2.8.0 and rtt-2.8.1
S Roderick <[email protected]> Sat, 13 Jun 2015 09:03:20 +0200
| Newsgroups | gmane.science.robotics.orocos.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============1578686899== Content-type: multipart/alternative; boundary="Apple-Mail=_B3D8ACB9-D115-49CD-8CF2-1DEB8A7D258F" --Apple-Mail=_B3D8ACB9-D115-49CD-8CF2-1DEB8A7D258F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Jun 13, 2015, at 00:16, Leopold Palomo-Avellaneda = <[email protected]> wrote: > Hi, >=20 > today Ruben Smits merged a pull request [1]. We had an interchange of=20= > comments about if it was ABI compatible or affects too much. >=20 > Well, this evening I have been playing a bit with a tool called > abi-compliance-checker [2]. >=20 > The result is here [3]. The verdict says Incompatible in (1.2%).=20 > I don't know if this is important or not, or we can trust it. I can = provide=20 > any file used or procedure if it's needed. >=20 > Best regards, >=20 > Leopold I guess the question is, what is the project=92s process regarding = choosing version numbers? IIRC there was some talk a while back about = using semantic versioning [1] to make these decisions. If that is a = direction that we want to take, then is a tool like the = abi-compliance-checker part of that approach? Otherwise, the maintainers = can choose whatever version numbering approach they like (good, bad, or = otherwise). Cheers S [1] http://semver.org= --Apple-Mail=_B3D8ACB9-D115-49CD-8CF2-1DEB8A7D258F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Jun = 13, 2015, at 00:16, Leopold Palomo-Avellaneda <<a = href=3D"mailto:[email protected]">[email protected]</a>> = wrote:<br><div><br class=3D"Apple-interchange-newline"><blockquote = type=3D"cite">Hi,<br><br>today Ruben Smits merged a pull request = [1]. We had an interchange of <br>comments about if it was ABI = compatible or affects too much.<br><br>Well, this evening I have been = playing a bit with a tool called<br>abi-compliance-checker = [2].<br><br>The result is here [3]. The verdict says Incompatible in = (1.2%). <br>I don't know if this is important or not, or we can trust = it. I can provide <br>any file used or procedure if it's = needed.<br><br>Best = regards,<br><br>Leopold<br></blockquote></div><br><div>I guess the = question is, what is the project=92s process regarding choosing version = numbers? IIRC there was some talk a while back about using semantic = versioning [1] to make these decisions. If that is a direction that we = want to take, then is a tool like the abi-compliance-checker part of = that approach? Otherwise, the maintainers can choose whatever version = numbering approach they like (good, bad, or = otherwise).<br><br>Cheers<br>S<br><br>[1] <a = href=3D"http://semver.org">http://semver.org</a></div></body></html>= --Apple-Mail=_B3D8ACB9-D115-49CD-8CF2-1DEB8A7D258F-- --===============1578686899== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Orocos-Dev mailing list [email protected] http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev --===============1578686899==--