John Carter wrote: > Alas, this is a bit of a problem. In that there are hundreds of > the @##$! things. And as I have found out, people tend to get a bit lax > about booking files in. (I found out the hard way, by moving from RCS to > CVS and finding nothing worked. People had been too lazy / forgot to book > things in to RCS.) (Perhaps this is altogether too obvious) The way out of this is to institute a process such that things will noticeably break if people fail to check things in. Have the build process (preferably automatically and periodically) do a fresh checkout or export and build from there. You _must_ do this anyway if you are to have any confidence that your CM process isn't hopelessly broken. You can't assume that it's working, you must test it regularly.
