This space is an archive space for documentation related to old versions of Fluid Infusion (i.e. versions before 1.3). For documentation related to the latest Infusion, see Infusion Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 35 Next »


About this Page

This document outlines our process for coordinating releases of the Fluid source code and the UX Toolkit.

On this Page:

What's in a Release?

We expect that each Fluid release will contain a combination of framework code, reusable user interface components, and documentation. More specifically:


  • JavaScript code for the Fluid framework
  • JavaScript, HTML, and CSS for Fluid components
  • Examples and sample code
  • API documentation and tutorials

UX Toolkit

  • UI Design Patterns
  • UX Walkthrough checklists and techniques
  • User testing guidelines

Frequency of Releases

Fluid intends to release versions of the Fluid framework, components, and UX Toolkit on a roughly quarterly basis. For more information about the specific timing of our releases, check out the Fluid Project 2007-9 Project Plan. The choice to release on a quarterly basis was made in order to:

  • Ensure that we test regularly
  • Regularly produce the important "collateral" material required to successfully use our code:
    • Documentation
    • Quality assurance tests
    • Fixes and work arounds for known issues
  • Provide stable, tested snapshots of our current progress in an easy-to-use form
  • Ease integration with Sakai, uPortal, and our other collaborating projects

Resease Version Number

Each release must have a unique version number associated with it, e.g. "0.1" or "0.3beta1". This version number must be recorded consistently in a few locations:

  • Wiki pages and other documentation
  • The project pom.xml file
  • The ant build scripts properties file, build-scripts/
  • The filename of the generated PDF documentation

The following instructions will describe more specifically when, where and how to record the release number.


As we approach an upcoming release, the following process kicks into gear:


Who Coordinates with the Community?

Identify the Release Manager

Project Manager, Tech Lead

Set the release date and code freeze date

Project Manager, Tech Lead, Release Manager

Coordinate the release deliverables

Project Manager, Tech Lead , UX Leads

Work with component design/development teams to produce a test plan for each Fluid component

QA Lead

Recruit QA testers

QA Lead

Create the Release Status page

Release Manager

Ensure known issues in JIRA have been marked with the correct fix version for the release

Release Manager

Discuss ongoing bug fixes and commits on fluid-work

Whole Community

Ongoing QA testing and bug fixing

Whole Community

Review commits

Release Manager

Generate the PDF Documentation

Release Manager

Tag and package the release

Release Manager

This is a collaborative process, and the community is encouraged to take an active role in defining schedules and coordinating the release process. It is expected that the Release Manager and QA Lead roles can be rotating positions based on interest and expertise.

About the Release Manager

The Release Manager is a volunteer from the community who agrees to be the primary point of contact for a release. The release manager's responsibilities includes:

  • Working with the technical lead and project manager to determine the timing of a release
  • Announcing the release schedule
  • Coordinating code freeze
    • Reviewing commits
    • Ensuring post-freeze commits are well-tested, filed against known JIRA bugs, and don't change public APIs
  • Managing the mechanics of a release, including:
    • Tagging the release
    • Creating a maintenance branch if necessary
    • Packaging up the release
    • Working with the project manager to announce the release

Release Status

Each Fluid release will have a status page, documenting the deliverables expected for the release. This includes a a list of new functionality, documentation, and the contents of the UX Toolkit. The status page will also outline all of the known bugs and issues that are expected to be fixed in time for the release. The release status page should also include a summary of the goals for the release.

How to Create the Release Status Page

The following summarizes the steps to create a release status page:

  1. In Confluence, create a new wiki page as a child of the Project Coordination page called "Fluid x.y Release Status" (where x.y is the version number).
  2. Document the release goals
  3. Create a table outlining the release deliverables, including the status and coordinator for each deliverable
  4. In JIRA, create a filter showing all of the open issues corresponding to the release.
  5. Save the filter and share it publicly. This may require special access in JIRA, so ask if you need help.
  6. Grab the URL to the RSS feed of the filter.
  7. Use the jiraissues tag in Confluence to automatically pull in the contents of the RSS feed and display it in a table:

How to Generate the PDF Documentation

The PDF documentation is generated by exporting relevant pages from the wiki. The wiki pages to include are generally categorized under "API Documents," "Tutorials" and "UX Toolkit."

The resulting PDF document will be included in the zip file with the source and examples.

How to Export the Wiki Pages

  1. Label the relevant wiki pages with the label "release."
    • The parent-child relationship of wiki pages will be reflected in the resulting PDF document table of contents. It is recommended that drafts of the PDF be checked for a reasonable structure, and if necessary, the parent-child relationships on the wiki be adjusted (note that this won't affect links within wiki pages).
  2. Produce a list of all the labelled pages, and keep it on hand.
  3. Export only the labelled pages:
    1. On the wiki, go the the' Browse Space' link in the navigation bar on the left, and then choose' Advanced'.
    2. Choose "Export Space"
    3. For 'Export format' choose "PDF Output"
    4. Turn off any extra options
    5. Clear all of the checked pages, then check only the pages labelled "release" (refer to the list you kept on hand. You kept it on hand, right?)
    6. Click the "Export" button at the bottom of the page.
  4. Rename the resulting PDF file using the version number, specifically "Fluid-{version number}.pdf"
  5. Edit the PDF file:
    1. Change the "Space Details" title to "Fluid Infusion v{version number}"
    2. Replace the box containing details with a paragraph that says

      These pages were exported from the Fluid wiki (, which combines information about development, project coordination, and user experience. Note that some of the links will redirect to the wiki.

    3. Change "Available Pages" to "Contents"

How to Tag and Package the Source Code

A major constituent of the release is the "source code". This is a collection of JavaScript, Java, html, css, build script, example, and unit test files that are tracked using the fluid source code repository. The main tasks to create a release of the source code are to tag the current revisions of the source files, and to bundle them into an archive (e.g., a zip file).

How to Tag the Source Code

Note that the Fluid-0.1 release is used as an example in what follows. If you are using these instructions for another release, remember to substitute the correct version number for occurrences of "0.1".

The steps to tag the source code are:

  1. Impose a source code repository freeze until the source code is tagged. Announce the freeze on the fluid-work mailing list (
    • 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:
    • Edit the maven project file(s) (pom.xml).
    • Set the contents of the <version> tag as appropriate, for example:
    • Edit the ant properties file(s) (build-scripts/
    • Set the contents of the <version> tag as appropriate, for example:
      fluid_version = 0.1
    • Commit these project files to the repository.
  3. Check out a fresh, clean working copy of the source code from the trunk.
    • Execute:
      svn co fluid-0.1
  4. Using this working copy, ensure that the build works.
    • In the fluid-0.1 folder, execute:
      mvn clean install
    • 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:
      svn copy 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 project on trunk to reflect that trunk development is now a snapshot of the next release version. For example:
  8. Commit the trunk's modified maven project file.
  9. Lift the prohibition of committing to the trunk of the repository by announcing same on the fluid-work mailing list (

How to Package the Source Code

The steps to package the source code are:

  1. Check out a fresh, clean copy of the tagged version of the source code.
    • Execute:
      svn co fluid-0.1
  2. Place the PDF documentation file in the root folder (i.e. as a sibling of the src folder).
  3. cd into the build scripts folder (fluid-0.1/build-scripts) and run the ant task to build the release bundle:
    This creates a folder called products and places the release bundles there:
    • This zip file should contain the PDF file and the license files, as well as source, examples, and the war file.
  4. Test the distribution file thoroughly by unpacking it into a clean environment and running all tests, etc.

Posting the Distribution

The distrbution file should be made available on the main project site's Downloads page ( and on the wiki's Latest Release page.

Managing Unexpected Issues

Bugs happen. When unexpected issues or problems arise, the Release Manager, Technical Lead, or Project Manager will inform the community and work with them to adjust the release schedule accordingly. If you find an issue that you think is a blocker, let the Release Manager know as soon as possible.

If you discover a security issue, follow the Fluid Security Policy and report the issue privately to the security team.

  • No labels