Hiding changes

[Ian S. Worthington]

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

Re: Hiding changes

[Scott Kostyshak]

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 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?

Hi Ian,

Is this what you are interested in?
http://www.lyx.org/trac/ticket/4140

Actually it sounds like you want something a little more general than
that. You want to hide specific changes, if I understand correctly.

Scott

Re: Hiding changes

[Paul A . Rubin]

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

Paul

Hiding changes

[Ian S. Worthington]

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

Re: Hiding changes

[Scott Kostyshak]

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 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?

Hi Ian,

Is this what you are interested in?
http://www.lyx.org/trac/ticket/4140

Actually it sounds like you want something a little more general than
that. You want to hide specific changes, if I understand correctly.

Scott

Re: Hiding changes

[Paul A . Rubin]

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

Paul

Hiding changes

[Ian S. Worthington]

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

Re: Hiding changes

[Scott Kostyshak]

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 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?

Hi Ian,

Is this what you are interested in?
http://www.lyx.org/trac/ticket/4140

Actually it sounds like you want something a little more general than
that. You want to hide specific changes, if I understand correctly.

Scott

Re: Hiding changes

[Paul A . Rubin]

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

Paul