Re: ada writing guide

["Samuel T. Harris" <samuel_t_harris@Raytheon.com>]

Ted Dennison wrote:
> 
> With revision control, we have:
> 
>   Monday Fred opens up an emacs session.
>   Tuesday, Joe opens up an emacs session, checks out the cap file, adds
> 3 capitalizations, and checks back in the cap file.
>   Wednesday, Joe checks out the cap file, adds 3 more capitalizations,
> and checks back in the cap file.
>   Thursday, Joe checks out the cap file, adds 3 more capitalizations,
> and checks back in the cap file.

Any version control system which allows Fred to simply check-out
the file without warning him that his content is no longer
based on the latest version is seriously broken! This is a
basic access control feature. If you want this protection,
then support of this feature becames a primary tool selection
requirement!

>   Friday, Fred checks out the cap file, adds 5 capitalizations, and
> checks back in the cap file. (wiping out all 6 of Joe's)
>   Monday, Joe checks out the cap file, adds 4 more capitalizations, and
> checks back in the cap file (wiping out Fred's 5)
>   etc.
> 

Our configuration management tool fails on Freds Friday check-out
because the version upon which he is basing his check-out is no
longer the latest version available. At that point, Fred can
try again and either accept the latest version before the
check-out (thus preserving Joe's changes) or forcing his
version to become the latest (because he KNOWS Joe's changes
are bogus).

-- 
Samuel T. Harris, Principal Engineer
Raytheon, Aerospace Engineering Services
"If you can make it, We can fake it!"