Share, Pin and Branch to Create Service Pack Projects (Bug Fixes)

If the need for a bug fix occurs after a project has been labeled and further developed, use the following share, pin and branch scenario. This will use a minimal amount of hard drive space.

To share, pin, and branch a project:

1. In the drive toward Version 2.0, develop and test your project (e.g., $/Application).
   
   
2. Label the project "Version 2.0."
   
   
3. Begin changing files in the project in the drive toward Version 3.0 of the project, which will introduce new features.
   
   
4. If you realize an interim Version 2.1 is needed for bug fixes, select the project. 
   
   
5. On the Tools menu, click Show History to display the Project History Options dialog box.
   
   
6. Select the Include Labels box.
   
   
7. Click OK to display the History of Project dialog box.
   
   
8. Select the label version "Version 2.0."
   
   
9. Click Share to display the Share From dialog box.
   
   
10. Select the project you want to be the parent of the newly created project.  This is usually the $/ project.  Also be sure the Branch after Share box is not checked.
    
    
11. Click OK to display the Share dialog box.
    
    
12. Give the project a New Name (e.g., $/Application V 2.1). 
    
    
13. If the project has subprojects, select Recursive. 
    
    
14. Add comments in the Comment box as needed, then click OK.
    
    
15. Click Close to exit the History of Project dialog box.
    
    
16. Select the newly created project (i.e., $/Application V 2.1).  All files in this project should now be pinned.
    
    
17. Select only those files that need to be changed to address bug fixes, then branch the file(s).  See Branch Shared Files for more information.  Leave pinned any files that do not need to be changed.

You can later merge bug fix changes back into your Version 3.0 project.