We have some technical documentation which used to be maintained by a single person who's now left us.
I'd like to make each developer responsible for making their own updates, with technical and stylistic approval resting with two other people. As the documentation is monolithic we can prevent simultaneous update loss by simple Windows file locking, and identify changes by enforcing change tracking. What I'm concerned about though is how I can temporarily hide an update which has been made but is not going to be released at this time without having to actually cut it out, publish, and then restore. Any ideas? Ian
