Thanks
Vivek
There are some usefull tips in it (certainly for me, as I am just a
newbie in CVS uasge).
Some remakrs after a quick look in your document:
The "Home" link does not work. I think you used docbook, maybe it is
usefull to generate a pdf or ps from the docbook sources. A more direct
link to the docbook sources would be usefull.
An example of the automation process (7.2) would be usefull. Also some
tips on "what you should not use CVS for" may be usefull.
Hope this was of some help,
Regards,
Kris
--
Kris Luyten
kris ad lumumba dot luc dot ac dot be
http://lumumba.luc.ac.be/kris
This is well written, and has good advice.
However, there are other branch policies that can be useful.
For example, the binutils gnu project does all development work on the
main branch, and only creates a branch for a release.
On my projects, I like to create a branch for each developer after
each release. Then each developer can check in stuff that may not yet
work, using CVS as a backup/revert tool (it's really good at that!).
Some people still insist on locking files, so only one developer can
edit at a time. It would be useful to have a solid discussion of why
that really doesn't work (or links to existing ones). I know there are
others available, but I don't have good links to them yet.
>
>
> Thanks Vivek
--
-- Stephe
Hello All
Version 0.2 is online. I have incorporated the various suggestions
given to me by the readers. Please have a look at the new version
http://www.geocities.com/vivekv/cvs-bestpractices/index-cvs-bestpractices.html
thanks
Vivek
http://www.geocities.com/vivekv/cvs-bestpractices/index-cvs-bestpractices.html
thanks
Vivek