Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Impose a source code repository freeze until the source code is tagged. Announce the freeze on the fluid-work mailing list (fluid-work@fluidproject.org).
    • Users are prohibited from committing to the source code repository trunk while the tagging operation is under way.
  2. Modify the release information in the necessary files:
    1. Edit the maven project file(s) (pom.xml and project.xml).
    2. Set the contents of the <version> tags as appropriate, for example:
      Code Block
      <version>0.1</version>
      
    3. Edit the ant properties file(s) (build-scripts/build.properties).
    4. Set the contents of the <version> tag as appropriate, for example:
      Code Block
      fluid_version = 0.1
      
    5. Ensure that the dependencies lists in build-scripts/build.properties are up-to-date:
      • The dependencies lists must include all of the file that are to be included in the bundle.
      • The order of occurrance of the files in each list must take into account any dependencies between the files.
    6. Update the README.txt file at the root of the package to reflect the current release information.
    7. Commit these project files to the repository.
  3. Check out a fresh, clean working copy of the source code from the trunk.
    • Execute:
      Code Block
      svn co https://source.fluidproject.org/svn/fluid/components/trunk fluid-0.1
      
  4. Using this working copy, ensure that the build works.
    1. In the fluid-0.1 folder, execute:
      Code Block
      mvn clean install
      
    2. The build should create a war file containing the fluid components. The war file is created in .../fluid-0.1/target/fluid-components-0.1.war, and is copied to the local maven 2 repository, .../.m2/repository/org/fluidproject/fluid-components/0.1/fluid-components-0.1.war.
  5. Run the jqUnit tests (by opening the HTML test files in a browser), and ensure that all succeed.
  6. Tag the source with the release version number.
    • Execute:
      Code Block
      svn copy fluid-0.1 https://source.fluidproject.org/svn/fluid/components/tags/fluid-0.1
      
    • Note that the above assumes that "fluid-0.1" is the directory containing the maven project file with the correct release version tag.
  7. Modify the version of the maven and ant project files (pom.xml, project.xml and build-scripts/build.properties) on trunk to reflect that trunk development is now a snapshot of the next release version. For example:
    Code Block
    <version>0.2-SNAPSHOT</version>
    
  8. Modify the fluid.version in Fluid.js
  9. Update the fluid version in all the javascript files
  10. Commit the trunk's modified maven project file.

...