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

The user manual for the Fluid packaged software releases consists of a set of information pages residing in the Fluid wiki. This Table of Contents lists all of the manual pages, organized under section headings. You can navigate through the manual by following the links below. To return to this page, click the link labelled User Manual ToC at the top of the left-side navigation bar.

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

We release versions of the Fluid framework, components, and UX Toolkit on a monthly basis. For more information about the contents of each monthly release, check out the Fluid Project 2007-9 Project Plan.

Release Version Number

Each release has 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:


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

Update Wiki pages

Tech Lead, UX Leads

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

Create snapshots of the wiki API documents

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:

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:

Updating the Wiki for Release

Updating Wiki: Development

  1. Update any development API and integration pages.
  2. Update any demos
  3. House cleaning - Delete any unnecessary pages and information created in this past iteration.
  4. Update download & component pages (see below)

Release download pages

  1. Consider putting a disclaimer at the top of any affected pages, with the following text (or something similar):
  2. Duplicate the old Fluid Infusion - Current Release page into a new page called "Fluid Infusion X.X" where X.X is the old release number.
  3. Update Fluid Infusion - Current Release to the latest release.
  4. Update the Downloads and Demos page to reflect any new demos that are now available.

Component pages

  1. Go to the Components page
  2. For each Component that was updated in this release, ensure that the relevant information page is updated.
  3. Update API, Integration, Demo, and Testing sections as necessary.

Updating Wiki: UX

  1. House cleaning - Delete any unnecessary design information (pages, notes, etc) added to the Wiki in this past iteration.
  2. Update any Components pages to reflect the current state of the design.
  3. Verify that any changes to the UX Toolkit is reflected.

How to Create a Snapshot of the Wiki API Pages

The following process should be carried out for two sets of technical documentation: API Documents and Tutorials:

  1. Start with the 'trunk' version of the first page in the set of documentation.
  2. Create a copy of the page.
  3. Rename the copy to include the version number, using the following convention:
  4. Adjust the parent document to be the appropriate already-versioned parent.
  5. Edit the {info} block at the top of the page to declare that this page refers to the versioned doc, and they should see the other docs for trunk docs, using the following template text:
  6. Check the page for any links to other version-specific pages, update the links.
  7. Preview the page to make sure it's ok.
  8. Save the page
  9. Return to the trunk version that you just created a copy of.
  10. Edit the {info} block at the top of the trunk page to refer to the new versioned page you just created (instead of the previous version that was there).

When all the pages have been snapshotted, edit the Table of Content page to reference the new versioned docs.

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 (
  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:
    3. Edit the ant properties file(s) (build-scripts/
    4. Set the contents of the <version> tag as appropriate, for example:
      fluid_version = 0.1
    5. Ensure that the dependencies lists in build-scripts/ 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.
  4. Using this working copy, ensure that the build works.
    1. In the fluid-0.1 folder, execute:
      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.
  7. Modify the version of the maven and ant project files (pom.xml, project.xml and build-scripts/ 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.
  2. 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:
  3. 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 Fluid Infusion - Current Release page.

Update JIRA

  1. Mark the version released, moving remaining open issues to the next version.
  2. Do a query for all unresolved issues that affect the previous release and release candidates. Add the new release version as an affected version for each issue in the results.

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.