Daily Build and Smoke Test Procedure

1. Finish ALL code modifications/additions.

2. Compile newly added code with private copy of current build status to ensure proper syntax and usages.

3. Execute the current smoke test with current private build status to ensure proper interactions and functionality.

4. After passing smoke test, check new source file(s) into the repository to be added into the next build.

5. Build team will run a total system build from repository files.

6. Run the current smoke test to ensure a build stable enough to withstand testing.

7. If any problems are incurred and do not allow the system to be tested (in other words if the build blows up) the developer who checked in the "TNT" code fixes the problem IMMEDIATELY - A WORKING BUILD IS PRIORITY #1.