You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@turbine.apache.org by dl...@apache.org on 2002/03/19 01:34:40 UTC

cvs commit: jakarta-turbine-site/xdocs/common release-process.xml

dlr         02/03/18 16:34:40

  Added:       xdocs/common release-process.xml
  Log:
  Beginnings of a release process document.
  
  Revision  Changes    Path
  1.1                  jakarta-turbine-site/xdocs/common/release-process.xml
  
  Index: release-process.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
  
  <properties>
    <title>Release process</title>
    <author email="dlr@finemaltcoding.com">Daniel Rall</author>
  </properties>
  
  <body>
  
  <section name="Release process">
  
  <ol>
    <li>
      Perform a successful build and test suite execution.
    </li>
    <li>
      Check out fresh working copy of CVS module you're going to tag.
    </li>
    <li>
      Set the release version number in Maven project.xml and/or Ant
      default.properties and commit the change to the version control
      repository.  For example, 3.0-dev would become 3.0-b1 or 3.0-rc1.
    </li>
    <li>
      Tag the release via <code>cvs -q tag
      <i>PROJECT_VERSION_MODIFIER</i></code>.  An example release tag is
      <i>TURBINE_2_2_B1</i> or <i>TURBINE_3_0_RC1</i>.
    </li>
    <li>
      Set the next development version number in Maven project.xml
      and/or Ant default.properties and commit the change to the version
      control repository.  For example, 3.0-b1 would become 3.0-b2-dev.
    </li>
  </ol>
  
  </section>
  
  </body>
  </document>
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>