PDoc-Software Up-issue Procedure

Created by: Lester Caine, Last modification: 12 Oct 2010 (13:12 BST)
Procedure for Up-issuing Software Release

1/ Produce Software Change Note

1a/ Detail reasons for this release

1b/ List any known omissions from this release

1c/ List DLL's required for this release

1d/ List all changes included as result of bug report

1e/ List changes in operation, additional features or wish list ammendments

1f/ Detail instructions for change of installed software on site

2/ Copy complete development directory to an archive and record issue number

2a/ Note state of Development Environment so that current system can be created

2b/ Store details of any additional used.

3/ Store copy of any additional code or notes with archive

3a/ In case of up-issue of DLL's or other modules used with Program, store copies

of new DLL's with archive.

4/ Build an Installation set

This is done manually rather than with automatic loader as it allows more control

The result may be more than one floppy disk

4a/ Copy of new program

4b/ Copy of any new DLL's

4c/ Copy of any new .INI's or other additional files

4d/ Copy of Change Note

5/ Check Installation Set on Target Machine

6/ Copy Installation Set to Archive

7/ Duplicate Archive on Re-writable Drive

8/ Either Supply Build Set and Printed Copy of Software Change Note

Or Email Build Set and Fax copy of Change Note

During development phase, updates are transfered electronically to speed process
&nbs