The main reason for generating baseline and change request reports is to be able to ascertain the content of a build or release. The difference between baseline and change request reports is as follows:
Note that there is something of a similarity between these two types of reports and what Configuration Management typically calls a Physical Configuration Audit and a Function Configuration Audit.
The generation of change request reports links back to the identification phase described in Chapter 1, "Introduction to Software Build and Release Management." During day-to-day development, when builds are being carried out frequently, change request reports allow project leads and management to identify the functionality in each build for monitoring and testing purposes. As you move toward release time, using the content of these reports is fundamental to being able to make proactive decisions about what and when to build and release. After reading this chapter, you will be able to
The mechanisms used in this chapter also will be of direct use in the next chapter, when we look at how to publish more sophisticated reports onto a project Web site or intranet.