-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Raye,
> Make ./trunk, ./branches, and ./tags REQUIRED subdirectories, not
> just "best practices". [Is it too late for this?!!!]
>
> These directories are automatically created when the repository is
> created. [Does this reduce flexibility too much?]
I know a few other people have already pointed out the reasoning for
why this is a horrible idea, but I just thought I'd throw in my two
cents.
One of Subversion's greatest advantages is the wide-ranging latitude
that gives to users when they're organizing their repository. The
branches/tags/trunk paradigm is a recommended practice because it makes
it easy for people to move from the CVS paradigm and organize things
relatively cleanly. However, it is -not- always a reasonable way for
repositories to be organized, especially if you're not storing source
code in your repository.
To help illustrate my point, I'm currently working on a book about
doing software development in Subversion, and I have an -entire
chapter- dedicated to the things to consider when deciding how you
should best organize your repository to fit with your project's
development pattern. If the organization is forced, all of that
flexibility goes away.
Also, if you search back through the archives of this list, you'll find
a number of interesting and lively discussions about good ways to
organize repositories that -aren't- branches/tags/trunk.
- -Bill
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFBUx1LSwe0AHUdEwQRAv/VAKCu/NE4mYsFCzHKnZXOAKFZWlVlrACgljsg
39j6hzn/18FhDci3bHXjbas=
=4+4o
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 23 21:01:07 2004