[JBoss-dev] CVS update: newsite CVSAdmin.jsp

[<mn...@us...>]

  User: mnf999  
  Date: 01/06/15 15:37:56

  Modified:    .        CVSAdmin.jsp
  Log:
  looking good on the <p>
  
  Revision  Changes    Path
  1.2       +9 -7      newsite/CVSAdmin.jsp
  
  Index: CVSAdmin.jsp
  ===================================================================
  RCS file: /cvsroot/jboss/newsite/CVSAdmin.jsp,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- CVSAdmin.jsp	2001/06/15 22:24:03	1.1
  +++ CVSAdmin.jsp	2001/06/15 22:37:56	1.2
  @@ -5,17 +5,18 @@
   
   
   <p class="head">INTRODUCTION
  -This document describes the JBoss CVS administration policies for managing
  +<p class="text">This document describes the JBoss CVS administration policies for managing
   the sourceforge cvs repository. Comments or questions regarding these polcies
   should be directed to the <a href="mailto:jbo...@li...">jboss-development mailing list</a>
   
   
   <p class="head">CREATING AND MANAGING RELEASE BRANCHES
  -The CVS branching and release management proceedures are outlined in this section.
  +<p class="text">The CVS branching and release management proceedures are outlined in this section.
   All development of new features occurs on the main trunk. Releases are done on
   branches off of the main trunk.
  -<p class="head">Release Numbering
  -Releases are tracked using CVS tags that have the following forms:
  +
  +<p class="head">RELEASE NUMBERING
  +<p class="text">Releases are tracked using CVS tags that have the following forms:
   <ul>
   	<li>Final Binary Releases: JBoss_&lt;major&gt;.&lt;even_minor&gt;.&lt;patch&gt;</li>
   	<li>Beta Binary Releases: Rel_&lt;major&gt;.&lt;even_minor&gt;.&lt;patch&gt;.&lt;build&gt;</li>
  @@ -59,7 +60,7 @@
   
   
   <p class="head">EXAMPLE RELEASE SCENARIOS
  -Consider events 1-12 in blue on the following figure:
  +<p class="text">Consider events 1-12 in blue on the following figure:
   <img src="pictures/cvs_structure.png" width="700" height="550" border="0" title="CVS Branch Structure" alt="CVS Structure">
   <ol start="0">
   <li>
  @@ -111,7 +112,7 @@
   <p class="head">CVS TASK HOWTO
   
   <p class="head">CHECKING CODE INTO THE MAIN TRUNK
  -New features and bug fixes on unreleased code should go into the main trunk
  +<p class="text">New features and bug fixes on unreleased code should go into the main trunk
   which is the latest development branch. The steps for doing this are:
   <ol>
   <li>Checkout the target module in which the changes are to be made. For example
  @@ -133,6 +134,7 @@
   </ol>
   
   <p class="head">CREATING A NEW BINARY RELEASE BRANCH
  +<p class="text">
   <ol>
   <li>
   Perform a clean check out of the jboss main branch without any tags to select the
  @@ -164,7 +166,7 @@
   </ol>
   
   <p class="head">CHECKING IN A PATCH ON A RELEASE BRANCH
  -When you have changes that need to go into the codebase of a release branch,
  +<p class="text">When you have changes that need to go into the codebase of a release branch,
   you need to check out that branch and make the changes. So for example,
   if you need to add a patch the the 2.2 branch of the example cvs structure
   above, you need to first check out the 2.2 branch using the Branch_2_2 tag.