A repo that acts as a project repository, showing the abanded branches of a project that don't have working trees

Registered by Tim Lind

It is important to be able to let the version control system keep revisions that are abandoned while keeping a clean working tree. However, Bazaar seems to have a confused concept of a shared-repository which takes away from the idea of maintaining a project's history behind the working tree we see. If a branch history is kept in the shared repository, then we should be able to query a repository as though it is the project (i.e. list all branches of this project) so when the repo stores related branches (one is an abandoned branch of another) we should be able to query that sort of thing, and this is specifically true when the branch working tree is deleted. In designing for distributed development Bazaar seems to have completely lost this notion of project store (that should obviously include abandoned branches).

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
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.

Subscribers

No subscribers.