You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by jv...@apache.org on 2002/03/24 18:49:52 UTC
cvs commit: jakarta-turbine-maven/xdocs release-process.xml

jvanzyl     02/03/24 09:49:52

  Added:       xdocs    release-process.xml
  Log:
  Adding dan's release process document and adding it to maven so that all
  projects using maven can benefit.
  
  Revision  Changes    Path
  1.1                  jakarta-turbine-maven/xdocs/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">
  
  <p>
    Turbine's release process consists of tagging one or more version
    control modules (Turbine and its dependencies).  For the 2.x
    development path, the module list to consider for tagging consists
    of the following:
    <ul>
      <li>jakarta-turbine-2</li>
      <li>jakarta-turbine-fulcrum</li>
      <li>jakarta-turbine-torque</li>
      <li>jakarta-turbine-stratum</li>
      <li>jakarta-turbine-maven</li>
    </ul>
    <!-- HELP: What about the TDK? -->
  </p>
  
  </section>
  
  <section name="Tagging an individual module">
  
  <ol>
    <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.  For example, 3.0-dev would become 3.0-b1 or
      3.0-rc1.
    </li>
    <li>
      Update any dependency changes (possibly caused by previous module
      tagging).  For Maven, this consists of modifying the
      <code>version</code> and <code>jar</code> attributes of each
      <code>dependency</code> element.
    </li>
    <li>
      Perform a successful build and test suite execution, and run the
      <i>clean</i> target to remove any generated files.
    </li>
    <li>
      Commit your changes to the version control repository.
    </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>