What about provide some metadata for branches ?

[Simon Rozet]

After having read all the answers, it seems that :

- Metadata should not be versioned
- It should not provide full rdf+doap record
- ... except maybe to be used with tools like webserver or google code

It can be usuful :

- for tools like webserver
- when you have a lot of bzr branches and you don't remember what the hell they are
or simply to know what is the purpose of a remote branch
(bzr meta http://foo.org/codes/bzrbranch)
- for google code

Jan Hudec wrote:
> Now I can see one reason to keep some metadata about branches. It's when you
> provide a revision browsing capability via bzrweb or similar tool. But
> I don't think this should contain a full doap record or anything similar.
> A .bzr/branch/branch-comment, similar to .bzr/branch/branch-nic would be
> about enough (and about what users might actually care to fill in).

I am not aware of .bzr/branch/branch-nic. What is this ?


Thanks for your comments.

-- 
Simon Rozet - http://atonie.org