Hiding changes

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

Re: Hiding changes

On Fri, Nov 8, 2013 at 11:45 AM, Ian S. Worthington ianworthing...@usa.net wrote: 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

Re: Hiding changes

You could put the document under version control, with provisional changes in branch, and release only trunk. Paul

Hiding changes

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

Re: Hiding changes

On Fri, Nov 8, 2013 at 11:45 AM, Ian S. Worthington ianworthing...@usa.net wrote: 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

Re: Hiding changes

You could put the document under version control, with provisional changes in branch, and release only trunk. Paul

Hiding changes

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

Re: Hiding changes

On Fri, Nov 8, 2013 at 11:45 AM, Ian S. Worthington wrote: > 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

Re: Hiding changes

You could put the document under version control, with provisional changes in branch, and release only trunk. Paul