Repository/Branch Layout

[Eugene Wee]

> I think tags is better. Tags can not only be used for released versions of
> a project.

 From what I understand, Subversion's tags/ directory convention is 
there because Subversion lacks tag support other than by copying, so it 
is given that whatever is in tags/ is a tag and should not be modified. 
As such, it makes sense for tags/ to contain more than just releases, 
since other milestones might need to be tagged.

With Bazaar's tag support, however, I am not sure if this approach still 
makes sense. Why create a convention where bzr tag should be used only 
in tags/ when one can tag anywhere as necessary?

The way I see it, trunk/ would be the main development branch, branches/ 
would contain experimental branches, /releases would contain release 
branches with release candidates, releases and bug fix releases tagged. 
Does this sound reasonable, yet not too far off "SVN-style"?

Regards,
Eugene