What we did at UBZ

[John A Meinel]

Aaron Bentley wrote:
...

> Centralized storage
> ===================
> http://bazaar.canonical.com/BzrArchives
> 
> We will introduce 'archives'.  Much like the archives in Arch, they will
> be structures that contain both branches and revisions.  They will not
> have working trees.  You will be able to name your branches pretty much
> anything, within the archive. (Except, maybe ./+storage)  Branch naming
> will be explicit, not implicit as in the centralized storage design I
> proposed.

I was thinking about this. What if we used
$archive/
  +archive/
    archive-format
    storage/
      weaves/
      ...
  branch/
  other/branch/foo/
  libs/
    libfoo/
    libbaz/
    ...

Basically, I'm thinking that rather than using +storage, which seems
nice for the actual storage information, but not very nice for all the
other information about this archive. That we switch to using +archive/
and then putting stuff underneath that.

Also, I'm a little concerned about the names which we give to the files
underneath a branch root, and having them collide with the path to the
branch.
For example if we have:

$archive/
  branch/
    branch-format
    revision-history
    parent

We can't have a branch named revision-history (or I guess we could, but
not in the same archive as a branch with a shorter path)
We could put everything back into a .bzr/ directory, and just disallow
that one name, or we could come up with some other non-colliding name,
since we know that dot files tend to get hidden by web-browsers, and it
can be nice to see actual files so that you know you have published
something. Hence why we were thinking +storage/

I'm just thinking out loud.

John
=:->


> 
> Differences from Arch:
> - Branches can safely be removed from archives
> - There are no naming rules
> 
> We're now referring to our current branches as 'standalone branches'.
> 
> To complement archives, we will introduce 'checkouts'. Much like CVS
> checkouts, these will be working directories that contain no branch
> data.  They will have a last-revision and a reference to a branch (which
> will often be an archive branch).
> 
> Bound Archive Branches
> ======================
> For many of us, bound branches and archives will combine nicely.
> I'll have a local archive both at home and at work.  All the branches in
> both archives will be bound to my remote archive, so that my public
> branches are always up-to-date.  I'll do all my work in checkouts, so
> branching will be extremely cheap, and will happen both locally and
> remotely at the same time.  (Somehow.  The UI isn't quite sorted)
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051114/012aa077/attachment.pgp