Bug Parade
- Justin Obara
Bug Parade
Overview
The bug parade involves a concentrated period of community-wide bug squashing. We focus on a set of the highest-priority open issues that affect components in the upcoming release. These inevitably include, but are not limited to critical and blocker bugs.
The amount of time spent in bug parade is variable, dependent on the number of high priority issues. The amount of time is set before the start of bug parade, by the Tech Lead, QA Lead, and or Project Manager, and can be lengthened or shortened as needed.
Please see the Coding and Commit Standards wiki page for the commit policy during bug parade.
Jira
Tagging
All jira issues that are to be part of the bug parade should be tagged with "Bug Parade X.X release", in either the jira description or as a comment to the jira.
Filtering
Two jira filters should be created: "Bug Parade X.X (all)" and "Bug Parade X.X (open)". The first filter will show all jiras tagged for the bug parade, the second will show only those which are still open.
Notification
The bug parade must be provided to the community via the fluid-work mailing list.
As bugs are closed, or require review, updates on the status of the bug parade should be distributed to the community via the fluid-work mailing list. Additionally, as the bug parade is not static, any additions/removals should also be communicated to the community. If the change is needed quickly it may be communicated on the Matrix Channel initially, but must be communicated through the fluid-work mailing list on the next update.
Sample Bug Parade e-mail
Needs Review:
Fluid-1999
Recently Closed:
Fluid-2073
JIRA filters:
(all) - http://issues.fluidproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=10128
(open) - http://issues.fluidproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=10129
commit standards:
Framework
Critical
FLUID-2059:
Reverse merge algorithm does not correctly preserve container objects
http://issues.fluidproject.org/browse/FLUID-2059
Pager
Blocker
FLUID-2046:
Renderer version of pager throws an error; using IE
http://issues.fluidproject.org/browse/FLUID-2046
Major
FLUID-2048: **CLOSED**
previous and next links are not displayed in the renderer version of pager; using Opera
http://issues.fluidproject.org/browse/FLUID-2048
FLUID-2047: **CLOSED**
page links are not displayed in front of the previous and next links in the renderer version of pager
http://issues.fluidproject.org/browse/FLUID-2047
UIOptions
Major
FLUID-2050: **CLOSED**
The content is not displayed if the layout is changed to "Simple" using IE 7
http://issues.fluidproject.org/browse/FLUID-2050
FLUID-2005: **CLOSED**
Only the top border and close button are visible when openning UI Options dialog: Using IE6
http://issues.fluidproject.org/browse/FLUID-2005
FLUID-1998: **CLOSED**
The font spacing, on the "Save and apply your preferences" button, does not change
http://issues.fluidproject.org/browse/FLUID-1998
FLUID-1986:
Font size only changes in the preview.
http://issues.fluidproject.org/browse/FLUID-1986
Minor
FLUID-1999: **REVIEW**
Pointer changes to a hand cursor over radio button text, but clicking doesn't select the radio button: Using IE 6
http://issues.fluidproject.org/browse/FLUID-1999
Uploader
Blocker
FLUID-2073: **CLOSED**
Ensure graceful degradation for "unsupported" browsers
http://issues.fluidproject.org/browse/FLUID-2073
Critical
FLUID-1982:
Uploader: after Upload stop, all delete buttons no longer function
http://issues.fluidproject.org/browse/FLUID-1982
FLUID-1824:
[Keyboard accessibility] doesn't appear to be a way to make an elm un-activatable
http://issues.fluidproject.org/browse/FLUID-1824
Major
FLUID-2020:
Uploads stop at position where files were removed from the queue, in flash 9
http://issues.fluidproject.org/browse/FLUID-2020
FLUID-2010:
Deleting uploaded files from the file queue will cause it to skip files and hang
http://issues.fluidproject.org/browse/FLUID-2010