Developers must 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 must set the current task so that objects they check
out are associated with the correct task automatically. If developers
do not follow these steps, they must perform several manual steps
to ensure that the patch includes the correct objects.
Also,
developers cannot complete any other work in
the patch projects. Other checked out versions must not be tagged
with the patch release value because they are then 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, install a copy of the released software to an installation area (for example, patch_test_1.2). Copy the products built for the patch into the area. (Ideally, install the patch the same way your customers install it.)
If you have a special utility for installing patches, use it instead.