Josef Wolf <jw@raven.inka.de> writes:
> When I think about 10 years ago, I would be _glad_ if there were an
> appendix "Good Praxices" in the CVS dokumentation. I had to learn it
> the hard way because there was no such appendix. I think most of us
> had to learn it the hard way, because there was no such appendix. Why
> do you want to force people to learn the hard way? The problem is that
> you can't easily correct most of those things reactive. If you don't
> do it right from the start, the remainder of the (repo-)life will
> claim for the sins of the early stages.
The authors of the CVS documentation had no way of knowing whether you
were versioning source code or kitchen recipes; they had no way of
knowing how many people were working on your project; they had know
way of knowing if you already had established practices in place.
The *only* thing they knew was that you need to learn to use CVS
(because otherwise, why would you be reading the documentation?). So
that's what they wrote about.
> Although this is true, I don't think it makes much sense to use svn
> without good practices. Failing to use good practices will result in
> failings to get benefits out of svn. Thinking this way, it makes
> no sense to use svn without good practices.
Huh? This is simply not true. You can get plenty of benefit from
Subversion, with no other practices at all besides just using a
version control system.
Are you claiming you got _no_ benefit out of CVS, when you used it
before having learned "good practices"? :-)
> But Anyway. Since it seems the svn core team don't like the "good
> practices" appendix reside in the main handbook, maybe there could be
> a consensus to create a separate good-practices-hadbook. While this
> would be overkill(*), I think it would be better than having nothing...
Hey, if you want to write a book on good practices, go for it! Even
feel free to post once on this list trolling for co-authors; it's
technically off-topic, but hey, we're easy... :-)
But such a book is outside the scope of "How To Use Subversion", and
needs to start its own mailing list, repository, web site, etc. It's
a separate project (and one which has probably already been done
several times; have you tried googling for some of this stuff?)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 23:41:07 2002