remove api_version concept

Bug #742192 reported by Martin Pool
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned
Breezy
Fix Released
Medium
Jelmer Vernooij

Bug Description

Bazaar added an "api version" concept, as distinct from the library version. But this at the moment seems vestigial: it's always set to the bzrlib version, and there is just one version marker across the whole library rather than it being fine grained.

I don't think it's realistic to keep the API stable enough that clients can check only this and not the implementation version. I also think having accurate fine-grained versioning on particular classes will be too hard and probably will not be checked accurately enough to give good protection.

Therefore I think we should probably just delete the concept, and have plugins make assertions about what actual bzr versions they do or don't support.

Related branches

Jelmer Vernooij (jelmer)
Changed in brz:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Jelmer Vernooij (jelmer)
milestone: none → 3.0.0
Jelmer Vernooij (jelmer)
Changed in brz:
status: Triaged → In Progress
Jelmer Vernooij (jelmer)
Changed in brz:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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