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.
Deprecated Release Process
About this Page
This document outlines our process for coordinating releases of Fluid Infusion.
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.xmlandproject.xmlfilesThe 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)The
antbuild scripts properties file,build-scripts/build.properties
The following instructions will describe more specifically when, where and how to record the release number.
Process
Task | 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 | Whole Team |
Release Manager | |
Ensure known issues in JIRA have been marked with the correct fix version for the release | Whole Team |
Create documentation JIRA issues and coordinate with community | Documentation Lead |
Work with component design/development teams to produce a test plan for each Fluid component | QA Lead |
Recruit QA testers | QA Lead |
QA Lead | |
QA Lead | |
Create release related JIRA issues for the main release tasks, and set them as blockers (once Bug Parade is complete) | Release Manager |
Coordinate QA and Code Freeze | QA Lead |
Coordinate Release Bundle QA | QA Lead |
Release Manager | |
Write release readme and use it as text for announce e-mail | Release Manager |
Write release news item | Release Manager |
Manage updating the READ Me | Release Manager |
Manage updating the website pages (index, downloads, infusion) with new version number | Release Manager |
Manage updating the Wiki | Release Manager |
Build, test, and release bundles | Release Manager |
Manage git project repo and update code for next Release | Release Manager |
Send release annoucement email to sakai-ui, jasig-ue, i-staff@ischool.utoronto.ca, fac-all@ischool.utoronto.ca, i-phd@ischool.utoronto.ca | 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, QA Lead and Documentation Lead roles can be rotating positions based on interest and expertise.