| Warning |
|---|
This page is currently being worked on. |
| Info | ||
|---|---|---|
| ||
This document outlines our process for coordinating releases of the Fluid Infusion source code and the Design Handbook. This is an archival document. |
| Section | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Frequency of Releases
We release versions of the Fluid Infusion framework, components, and Design Handbook on a monthly basis. For more information about the contents of each monthly 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:
...
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 |
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 | |
Send release e-mail and create release news item | Release Manager |
...
| Anchor | ||||
|---|---|---|---|---|
|
Release Status Wiki Page
| Include Page |
|---|
...
|
...
|
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Issue Title | Issue Description |
|---|---|
"Tech review of <page> docs"
| A technical review of <link to actual documentation page>
|
Update the wiki for release | See http://wiki.fluidproject.org/display/fluid/Release+Process#ReleaseProcess-UpdatingtheWikiforReleasefor details |
Update the website for release | See http://wiki.fluidproject.org/display/fluid/Release+Process#ReleaseProcess-UpdatingDemosontheFluidProjectwebsitefor details |
...
- 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 and Demos page.
- Update the Downloads page to reflect any new demos that are now available.
...
How to Tag and Package the Source Code
| Include Page |
|---|
...
|
...
|
...
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.
...
If you discover a security issue, follow the Fluid Security Policy and report the issue privately to the security team.