Explicit facilities in bzrlib for different-model repositories.

Registered by Robert Collins

As we upgrade bzr's data model we need to keep interoperating with old format repositories, and for somethings like testaments and bundles we need an exact representation of the objects for that model. We should add a small, constrained facility to bzrlib to allow getting an old model of a Revision and RevisionTree, but have the entire codebase be built around the latest data model. This reduces the opportunity for serious bugs, because rather than having conditional code in multiple places, only points-of-conversion will need to know there have ever been multiple models.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Robert Collins
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.