Wireshark-dev: Re: [Wireshark-dev] [Wireshark-core] Working up to a new stable branch (1.6)
From: Balint Reczey <[email protected]>
Date: Tue, 31 May 2011 14:18:43 +0200
[Moving thread to wireshark-dev from wireshark-core, following Joerg's action]

I have just committed the make target "dumpabi" for dumping ABI
description using ABI compliance checker [1].

Now everything is there to start versioning with as little effort as possible.

Cheers,
Balint

[1] http://ispras.linux-foundation.org/index.php/ABI_compliance_checker

On 05/30/2011 02:23 PM, Balint Reczey wrote:
Most patches has been merged which would allow us to easily update the library
versions.

The important change I can't introduce by submitting a patch would be a change
to the release process. We should ensure that we don't make major and
maintenance releases without adjusting the library version according to the ABI
changes and we should not make maintenance releases with changes bumping the
library versions too high, e.g. to an existing major library version.

What is missing is a script for checking the ABI changes, but I'll try to
prepare one.

Cheers,
Balint

On 05/18/2011 11:16 PM, Jeff Morriss wrote:
Why not create a patch?

If this is only to maintain the ABI within a (stable) trunk, it doesn't
seem to do any harm.  And would then linuxtesting.org (only) warn us
about ABI breaks within a particular version of the library?

Balint Reczey wrote:
Ping...

We broke ABI again according to
http://linuxtesting.org/upstream-tracker/versions/wireshark.html .

What should be done (from my side) to start versioning?

Thanks,
Balint

On 05/15/2011 02:24 PM, Balint Reczey wrote:
On 01/12/2011 02:55 PM, Balint Reczey wrote:
On 01/04/2011 06:26 PM, Jaap Keuter wrote:
...
      Therefore I would like to hear from you what needs to be done, what
      loose end are still there (other than hoovering the Bugzilla
patches).
      I've got some ideas myself, but you probably have a better
outlook on
      things. No grand plans, just getting thing completed (hopefully in
      time).
Hi,

I think since we export only the symbols listed in .def/.sym files we
could
start keeping our API/ABI stable in stable branches and start library
versioning.

We could start by bumping the major version of the libs we ship
(libwiretab,
libwsutil, libwireshark) in 1.6.0.

In 1.8.0 we could remove the obsolete exported symbols if there is any.

Cheers,
Balint
Hi,

Could we please start managing the lib versions with 1.6.0(rc1)?

Thanks,
Balint