Kenneth Wood wrote:
> I, too, have seen great resistance, in my case by tech writers,
> to putting documents into any kind of source control system
> Yes, they develop documents just as coders develop
> code. But, they don't understand why "zipping up all
> my files and putting a copy on the shared drive" every
> day isn't a very good revision control process...
Keep asking them what they changed on some particular day last month
until they get the idea - or how their version differed from someone
else's work. More importantly, arrange the work flow so the only way to
move things from someone's individual work to testing/review is
through the revision control system and the only way from there to
production is by checking out a tagged revision. This works out
naturally with source code and a formal QA process since you need a way
to gather all the bits in one place and bless them anyway - and all the
tools already expect to interact with cvs or subversion. With other
kinds of work you may have to revise the process to make subversion the
easiest way to get things between any two points.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 27 23:30:02 2007