Precedent

RE: Felix SVN trunk root

Felix SVN structure model:

/felix
  /trunk
    /framework
    /std-bundles
      /cm
      /http
      /log
      ...
    /bundles
      /obr
      ...
    ...
  /releases
    /cm-1.0
    /framework-0.9
    /framework-1.0
    /log-1.0
    ...
  /sandbox
    /akarasulu
    /erodriguez
    /tbennett
    ...

SVN usage guidelines:

It is impossible to checkout/update Directory in one go without
getting all the branches, tags and other such things. Commons works
around it with externals, but that has its drawbacks because you are
forced to pick a protocol (https), for example.

Personally, I don't use tags and branches at all. Code that are
released, are copied into a proper directory named "releases", and
straight after made read-only. Branches are handled differently
depending on whether it is an "experiment" (in which case it is just
copied to my laboratory) or it is "maintenance" of released code, in
which case I first copy the "release" into a temporary area, do the
changes and then create a new "release" make readonly and so forth.

Also agree about the branch handling that seem to imply a very
diciplined use of branching. My experience this far of having one branch
for "the next generation" and one "stable branch" is that it diffuses
community energy and that it takes for ever to get to the next
generation of the product and that most of the original arguments for
creating a branch not are fulfilled in the end.