When a project is updated based on process rules, update re-evaluates which baseline project it should use. It checks the process rule to find the baseline, then checks the baseline to identify a version of the project. If multiple versions of that project exist in the baseline, update compares the platform values to select the project that has a matching or compatible platform value.
For example, when the editor-bob project is updated, update checks the process rule and finds that the latest baseline is selected. It then identifies the latest baseline matching the template criteria, for example, 20070115. It then checks baseline 20070115 for a version of the editor project to use as a baseline project.
If no version of a project is found in the baseline, that project is updated without a baseline project. This means that object versions that are not associated with any tasks for the current release are not considered candidates, and are not selected when you update the project. Some directory entries might be left empty in this case.
Therefore, it is important to include all projects in your application in the baseline, even those that have not changed since the last baseline. (Static projects can be reused in multiple baselines.)