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
- 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.xmlfile, which has a dependency on Infusion (see Tagging the Source Code for instructions)
antbuild scripts properties file,
Who Coordinates with the Community?
Set and announce the release date, code freeze date and bug parade date
Project Manager, Tech Lead, QA Lead
Coordinate the release deliverables and create a roadmap on the wiki
Project Manager, Tech Lead , UX Leads
Review the escalated issues
Ensure known issues in JIRA have been marked with the correct fix version for the release
Create documentation JIRA issues and coordinate with community
Work with component design/development teams to produce a test plan for each Fluid component
Recruit QA testers
Create release related JIRA issues for the main release tasks, and set them as blockers (once Bug Parade is complete)
Coordinate QA and Code Freeze
Coordinate Release Bundle QA
Write release readme and use it as text for announce e-mail
Write release news item
Manage updating the READ Me
Manage updating the website pages (index, downloads, infusion) with new version number
Manage updating the Wiki
Build, test, and release bundles
Manage git project repo and update code for next Release
Send release annoucement email to sakai-ui, jasig-ue, email@example.com, firstname.lastname@example.org, email@example.com
Release Status Wiki Page
Code cleanup for release x.x
Verify dependencies for components
This issue should be resolved in bug parade. Look at FLUID-2525 for an example of how to create the jira issue
Check licenses and copyrights
Update and expand on unit test coverage
Increase unit test coverage and ensure that all tests are passing.
screen source files for DOS line ending
Run source tree through an utility like dos2unix to normalize line endings for Unix. //
Turn off debug mode
Update fluid.fail() to throw an error, turn off debug mode for the renderer, etc. //
- 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."
- 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.
- 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.
How to Tag and Package the Source Code
If you discover a security issue, follow the Fluid Security Policy and report the issue privately to the security team.