Deprecated Release Process

Frequency of Releases

We release versions of the Fluid Infusion framework and components on a regular basis. For more information about the contents of each release, check out the Fluid Community Roadmaps.

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:

• git tags (historically SVN tags)
• Wiki pages and other documentation
• The project pom.xml and project.xml files
• The perma-comment at the top of the Fluid.js file
• The Infusion source code (each .js file - this is not modified for point releases such as 1.3.1)
• The ImageGallery web/pom.xml file, which has a dependency on Infusion (see Tagging the Source Code for instructions)
• The ant build scripts properties file, build-scripts/build.properties

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

Process

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, QA Lead and Documentation Lead roles can be rotating positions based on interest and expertise.

Release Status Wiki Page

Release-related JIRA issues

The real work of creating a release is managed through a number of Blocker JIRA issues. These JIRAs must be created for each release, and any necessary changes to the code must be committed against them.

During Bug Parade

Removing DOS CR/LF

For Ubuntu using fromdos command:

find . -type -exec fromdos '{}' \;

Get fromdos by running sudo apt-get install tofrodos.

After Bug Parade is Over

Try to identify any dependencies between JIRAs (for example, the bundle must be tested before it is posted) and create these links in JIRA.

Documentation JIRA issues

To ensure that the API documentation and tutorials are up-to-date, each document needs to be reviewed. JIRA issues should be created to coordinate this process. The specific pages needed will depend on the current state of the documentation, but the JIRAs should follow the following pattern:

NOTE: Technical review should ideally be carried out by someone who did NOT originally create the page!

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):
   • "This page is currently being edited in preparation for the pending X.X release. It's contents should be considered in flux and unreliable until this warning is removed. For the latest stable release, see Fluid Infusion X.X."
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.
   • _This new page should be a child of Fluid Infusion - Current Release.
3. Update Fluid Infusion - Current Release to the latest release.
   • Be mindful to follow the excerpt format. The links to the bundles at the top will be excerpted, and displayed on the Downloads page.

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.
   • Wireframes, Storyboards, Design pattern, Functional Req, User Testing, Story Cards, User modeling, Accessibility.
3. Verify that any changes to the Design Handbook is reflected.

How to Tag and Package the Source Code

Posting the Distribution

The distribution files must be uploaded to the websites releases folder using ftp. Links on the website downloads page (http://fluidproject.org/index.php/download-infusion) and the wiki downloads page will link to this location.

Speak to someone on the project core team about ftp access.

Updating Demos on the Fluid Project website

1. Archive the existing Demos page (http://fluidproject.org/index.php/infusion-demos) as follows:
   • Create a new sub-page of the Demos page and copy and paste the Demos page content there.
2. Extract a copy of the new minified source code and demos into the new releases' directory. (i.e. ~/website/docs/releases/0.999beta1)
3. update the Demos page links to reference the new sample code.
   • add any new Demos
4. Add a link from the Demos page to the Demos just archived in Step 1. Put this link under the "Past Releases" section at the bottom of the page.

Update JIRA

1. Mark the version released and ask the community to update the remaining open issues:
   1. The current assignee should consider the issue and decide whether or not to resolve it, assign to someone else, or change the "Fix for" version to an unreleased 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.