How bad is its impact? (Severity)
The fix needs to occur now because the issue:
- Is likely to generate a customer support call
- Significantly impacts the operation of a primary release driver feature
- Is an in-your-face issue that will touch the majority of users
How often does it happen? (Frequency)
Every time a user requests help on an affected subcommand.
How much effort is required to fix it? (Cost)
Approx 4 writer days (3 writers working 1 day each on the fixes, + 1 day for integration and testing)
What is the risk of fixing it? (Risk)
Does a work around for the issue exist? Can the workaround be reasonably employed by the end user?
Yes - deliver the fixes only in the version that is published on the web.The workaround could be employed by an end user but only if the user is aware of the workaround.
If the issue is not fixed should the issue and its workaround (if applicable) be described in the Release Notes?
How long has the bug existed in the product?
The errors were introduced in this release.
Do regression tests exist for this issue?
Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
QuickLook would be sufficient for this purpose.
When will a tested fix be ready for integration?
Before the RC 3 build is started.