When you create a baseline, you choose a list of projects to be in the baseline. Be sure to include all related projects in your baseline so that you have a complete set for reference.
Any projects that are already in a static state are included without further change. For each project that is not static (for example, a build management project), the following actions occur when the baseline is created:
The original build management projects and their work areas are left unchanged. The benefit is that they will continue to be rebuilt incrementally. If the build management projects were checked in and new prep versions checked out from them, they would be entirely rebuilt because uncontrolled intermediate products would not be in the newly checked out projects' work areas.
After creating a baseline, you can make work areas available for other users by turning on work area maintenance for selected projects in the baseline project, which will write it out to the work area. Typically, you will want to do this for absolute subprojects if developers reuse the static subprojects rather than checking out their own versions. The following commands are examples of how to query the database, then turn on work areas:
ccm query "is_project_in_baseline_of (baseline('20070203')) and name match '*_ext_x' and platform='UNIX'"