previous | next
 
home  |  search  |  contact  
  
 
 Introduction 
 BitKeeper Concepts  
 Getting Started  
 Advanced Operations 
 Advanced Topics 
 Reporting and Data Mining  
      - File Level 
        . File State Information  
        . File revision history 
        . File Contents 
      - Project Level 
        . Viewing Project History 
        . Viewing ChangeSet Contents 
        . Viewing Tagged ChangeSets 
        . Command History 
      - Debugging with BitKeeper 
        . Build Bugs 
        . Functionality Bugs 
      - Code Reviews 
        . Queue 
        . Process 
      - Reporting with Scripting 
      - BK/Web 
 Appendix A: Installation 
 Appendix B: Administration 
 Site Map 
     
Process
The process to go through is:
  • Engineer creates a repository which is a clone of the gate and then develops the new feature. Use hardlinked clones, if possible, as it takes up less space.
  • Engineer feels the feature is ready and creates a symlink to the repository in the ready directory of the appropriate queue.
  • Engineer sends email to the reviewers that feature is queued.
  • Reviewers review and add comments to feature.REVIEWED.
  • If the feature is accepted the "gatekeeper" can pull the change into the gate and move all feature related repositories and files to the done directory.
  • If the review comments are negative then the engineer does a

    bk fix -c

    on the repository, fixes the problem, and starts the review process again.

Home    Company    Products    How to Buy    Downloads    Contact Us    Documentation    Support    Site Map

© 1997-2005, BitMover, Inc.