Rev 975: Add repository layout spec. in file:///data/jelmer/bzr-svn/layout/

[Jelmer Vernooij]

At file:///data/jelmer/bzr-svn/layout/

------------------------------------------------------------
revno: 975
revision-id: jelmer at samba.org-20080322030540-jip3jh96fycgsxof
parent: jelmer at samba.org-20080322021233-ooblxnxj7944y27f
committer: Jelmer Vernooij <jelmer at samba.org>
branch nick: layout
timestamp: Sat 2008-03-22 04:05:40 +0100
message:
  Add repository layout spec.
added:
  specs/layout.txt               layout.txt-20080203230450-3jog72dlme7x4su4-1
=== added file 'specs/layout.txt'
--- a/specs/layout.txt	1970-01-01 00:00:00 +0000
+++ b/specs/layout.txt	2008-03-22 03:05:40 +0000
@@ -0,0 +1,44 @@
+Repository layouts
+==================
+
+.. contents:
+
+Rationale
+---------
+Branching schemes are very inflexible and changing them breaks the ability to 
+use the repository since they are embedded in the generated revision ids. It 
+should be possible to get rid of branching schemes but there are a couple of 
+properties of it that should still be usable. 
+
+When searching for revision ids, we need to search a limited set of paths in 
+the repository for branch properties.
+
+When importing a branch, we need to import the relevant tags. 
+
+Since there may be more than one project in a repository and it can be 
+very inefficient to have to browse the full repository it will be useful 
+to be able to restrict the paths searched on a per-project basis.
+
+Proposal
+--------
+In order to deal with this information, we need to keep a list of branches
+and tags per project.
+
+Storage
+-------
+It should be possible to specify the repository layout locally as the user 
+may only have read-only access to the repository. It should be possible to 
+set the layout globally as well, inside of the repository, so it is possible
+to use the repository and just have it work.
+
+If repository layout is known, one should be guess - similar to the way 
+that is currently being done for branching schemes.
+
+Backwards compatibility
+-----------------------
+Branching schemes should be derivable from the repository layout. 
+
+Implementation
+--------------
+
+.. vim: ft=rest