The_Maintenance_and_Documentation_of_Alto_Subystems_Feb75.pdf part of xerox The Maintenance and Documentation of Alto Subystems Feb75 The_Maintenance_and_Documentation_of_Alto_Subystems_Feb75.pdf, xerox alto memos_1975 The_Maintenance_and_Documentation_of_Alto_Subystems

Text preview for : The_Maintenance_and_Documentation_of_Alto_Subystems_Feb75.pdf part of xerox The Maintenance and Documentation of Alto Subystems Feb75 xerox alto memos_1975 The_Maintenance_and_Documentation_of_Alto_Subystems_Feb75.pdf

Back to : The_Maintenance_and_Docum | Home

TO: ALTOUSERS February 24, 1975
FROf.1: B. Hunt
SOBJECT: THE MAINTENANC~ AND DOCUMENTATION OF ALTO SUB-SYSTEMS.

The following are some ideas which I have r~garding the
implementation of new releases of altri software. I would appreciate
any suggestions whi~h you may have which would be beneficial in
establishing an acceptable procedure for handling the maintenance
and documentation of alto sub-systems.

1. The Maxc Directories.
The maintainer of a sub-system, when he has a new
release. would submit the following ~ackage to me:
a) The name of the source fi1e(s).
b} The name of an @-file which may be used to
create the new executable file(s") from this
source.
c) A message describi~g the changes which will
be effective "with this release. "The subject ~f
this message should be the name ~f the sub-system.
In the case of emergency changes. he may update
the At the same time, the items listed above should be sent
to me.
He will keep development copies on his personal
directory.

I will maintain the following:
"" a} The current directory will contain both the source
fi"les and the @-files. for new releases.
It will also contain the source files for
library subroutines.