Thomas Beale wrote:
> I have used many CM systems, and have been thinking about whether
> subversion supports the kinds of processes needed in real development,
> particularly release management. I think that the basic advice of using
> the trunk/tags/branches directories is ok, but does not go far enough.
That is, "real development" in your world of real development.
Everyone's world of real development is slightly different. The above
statement made it sound like Subversion is a toy versioning system not
used in "real development".
> We have so far defined the following in our repositories:
>
> - TRUNK: mainline current development;
> - BRANCHES: branch developments for new or alternative or test
> work;
> - TAGS: named baselines (no changes allowed)
> - RELEASES: release branches, i.e. branches corresponding to
> stable major points in the mainline (trunk) development,
> whose only further allowed changes are bugfixes.
>
> This corresponds more or less to the recommended way in Subversion of
> separating mainline development; the only difference is that in our
> project, upper-case directory names have been chosen to make the special
> status of these directories clear in a check-out structure, and the
> RELEASES directory has been added.
>
> "Releases" are really a kind of brnch but one where the allowed types of
> change is restricted to bugfixes. "Branches" are usually understood to
> be rela development changes.
>
> It would be good if subversion a) supported a standard directory
> structure like this, and b) if the tools could hide these directories
> (at least on the client side) and instead show them as 'views' - i.e.
> the user would be in the mainline view, the branch-xyz view, the
> release-0.8 view and so on. I don't think it would be hard to do.
Subversion does not impose any directory structure on you. Subversion
supports whatever directory structure you want. If I wanted to, I could
have a directory structure like this:
- foo
- BAR
- pOoP
and Subversion would still work as wonderfully as it does with the
defacto standard of trunk, branches, tags. Uppercase, lowercase,
naming. It is totally up to you.
As for clients hiding those directories, you would have to customize one
of the many available clients (they are open-source after all) since
what you are trying to hide is your own idea of a "real development"
directory structure.
--
Sly
This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 29 02:45:16 2005