Zorba

Introduce ABI compatibility check

Bug #867222 reported by Chris Hillery
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zorba
Confirmed
High
Chris Hillery
Zorba 3.0 "Kratos"

Bug Description

Going forward in 2.x releases, we need to ensure backwards compatibility at both the source and binary levels. There are certain API changes that would be backwards-compatible if clients recompiled their code, but would not allow simply re-linking against a later release; we need to avoid those changes.

One possibility would be an "ABI checker" as part of the remote queue run; I seem to recall seeing such software, somewhere...

Matthias Brantner (matthias-brantner)
Changed in zorba:
importance: High → Medium
Revision history for this message
Chris Hillery (ceejatec) wrote :

I would suggest leaving the Importance of this bug at "High", but targeting it for 3.0. The next major release is when we should get serious about maintaining real backwards-compatibility.

Revision history for this message
Chris Hillery (ceejatec) wrote :

This came up in discussions with the Fedora project maintainer for Zorba. We need to come up with a consistent and appropriate ABI-versioning scheme for our .so files, and once we have that, we need tests to assure that we don't break ABI compatibility without a corresponding version number bump. This needs to be sorted out no later than Zorba 3.0.

Changed in zorba:
milestone: none → 3.0
importance: Medium → High
status: New → Confirmed
Dana Florescu (dflorescu)
tags: removed: build-scripts v2.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.