Created: 2005-10-27 by JamesBlackwell
Implementation branch: none yet
At the moment much of the resposibility for keeping consistency within a branches stores lies in the Branch Object. It may be better to factor out all the storage logic into a BranchStorage or StorageLayer concept. This would then be used by a branch to access storage, and provides an entry point into the SharedStorage concepts.
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.
In place of Description of Issue here, add your own title that provides a description of the issue, or intended funcionality, or proposed change. You can have subsections that better describe specific parts of the issue; you can also include here subsections like the following:
It is important that the description section covers the functionality-related aspects (the "what") of the change. Providing rationale (the "why") is always a plus.
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
Should cover changes required to the UI, or specific UI that is required to implement this
Code changes should include an overview of what needs to change, and in some cases even the specific details.
This section should house the larger issues that need discussing; you can sprinkle XXXs around the page if you want to keep the smaller open issues in context.