Developers will need to copy a new development project from the baseline release, set their current task, diagnose and fix the problem, unit test, then complete the current task.
Developers who are fixing problems must set the release value on their projects before checking out files. They will also need to set the current task so that objects they check out will be associated with the correct task automatically. If they forget these steps, they will have to perform several manual steps to ensure that the patch includes the correct objects.
Also, developers should not complete any other work in the patch projects. This is so that other checked out versions are not tagged with the patch release value and included in the patch accidentally.
You can follow the same steps to create the system testing project with the following exception:
Copy only the projects to be included in the patch.
See Creating the system testing projects (page 55).
To set up a test area for the patch, you can install a copy of the released software to an installation area (e.g., patch_test_1.2), then copy the products built for the patch into the area. (Ideally, you should install the patch the same way your customers will install it.)
If you have a special utility for installing patches, use it instead.