[Sharpcvslib-commits] www branches.html,1.1,1.2

[<dr...@us...>]

Update of /cvsroot/sharpcvslib/www
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31823

Modified Files:
	branches.html 
Log Message:
Updated branch documentation.

Index: branches.html
===================================================================
RCS file: /cvsroot/sharpcvslib/www/branches.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** branches.html	2 Feb 2004 05:32:53 -0000	1.1
--- branches.html	18 Feb 2004 03:25:01 -0000	1.2
***************
*** 26,46 ****
              <a href="http://sharpcvslib.sourceforge.net/nightly-build/tests/">tests</a>
          </div>
!         <table>
!             <tr>
!                 <td>TODO: Writeup branch information</td>
!             </tr>
!             <tr>
!                 <td>To Checkout the release branch for version 0_35 use the following commands:
!                     <br />
!                     Developer:
!                     <br />
!                     cvs -d:ext:[username]@cvs.sourceforge.net:/cvsroot/sharpcvslib co -r Release_0_35_branch -d sharpcvslib_0_35_branch sharpcvslib
!                     <br />
!                     Anonymous:
!                     <br />
!                     cvs -d:pserver:ano...@cv...:/cvsroot/sharpcvslib co -r Release_0_35_branch -d sharpcvslib_0_35_branch sharpcvslib
!                 </td>
!             </tr>
!         </table>
      </body>
  </html>
\ No newline at end of file
--- 26,72 ----
              <a href="http://sharpcvslib.sourceforge.net/nightly-build/tests/">tests</a>
          </div>
!         <div class="Content">
!             <h1>Branching in Sharpcvslib</h1>
!             <p>
!                 Branching in sharpcvslib has been used primarily to maintain a stable code base for releases.
!                 With this in mind the strategy for branching (at the time this document was written) is to
!                 branch when the code is feature complete for the release and nearing a stable condition.  A 
!                 branch will then be made with the intent that only minor bug fixes will be applied to the 
!                 branch.
!             </p>
!             <p>
!                 When it is nearing time for another release the process will be completed and the existing
!                 branch will then be conceptually marked "closed".  The stabalization process will then repeat
!                 for the new release cycle.
!             </p>    
!             <table border="2">
!                 <tr>
!                     <td>Branch Name</td><td>Purpose</td><td>Active</td>
!                 </tr>
!                 <tr>
!                     <td>Release_0_35_branch</td><td>Maintenance of Release 0.35</td><td>true</td>
!                 </tr>
!             </table>    
!             <h1>Quick Reference</h1>
!             <p>
!                 Developer:
!                 <br />
!                 <code>cvs -d:ext:[username]@cvs.sourceforge.net:/cvsroot/sharpcvslib co -r [branch_name] -d [override_directory] sharpcvslib</code>
!                 <br />
!                 Anonymous:
!                 <br />
!                 <code>cvs -d:pserver:ano...@cv...:/cvsroot/sharpcvslib co -r [branch_name] -d [override_directory] sharpcvslib</code>
!                 <br />
!                 where:
!                 <ul>
!                     <li>
!                         <code>[branch_name]</code>: the name of the branch you are interested in, for instance Release_0_35_branch.
!                     </li>   
!                     <li>
!                         <code>[override_directory]</code>: the directory that the sources should be checked out in instead of the module directory, for instance use sharpcvslib_0_35_branch.
!                     </li>
!                 </ul>    
!             </p>    
!         </div>    
      </body>
  </html>
\ No newline at end of file