Scott Lamb <slamb@slamb.org> writes:
> Why?
>
> This information would be helpful. These are particularly important
> when using SCM systems. Subversion now is getting relatively
> experienced users who have used CVS, were dissatisfied, and are
> willing to be on the bleeding edge to get something better. But
> post-1.0, there will users who have never used another SCM system and
> are not familiar with these ideas.
>
> The chapter could be called "Good SCM Practices" to clarify it is not
> Subversion-specific.
A brief rant:
The challenge in writing documentation is deciding what not to
include. Technical books typically run *over*, not under, their
projected page count. If we're not careful, we'll have an enormous
doorstop in which casual browsing is punished by acres of off-topic or
redundant material. (Sound familiar? Sound like a lot of technical
books you've seen? :-) ).
Good SCM practices are completely independent of Subversion. You can
use SVN without good practices. You can have good practices and yet
not be using SVN.
Let's please keep non-Subversion material out of the handbook.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 16:39:22 2002