Revision as of 15:04, 22 March 2010 by Mbalin (Talk | contribs)

NetBeans 6.9 Bug Waiver Process

  • Issuezilla Keywords for NetBeans 6.9
  • 6.9_WAIVER_REQUEST - when asking for waiver (issues)
  • 6.9_WAIVER_APPROVED - when waiver was approved by team (issues)


High-priority bugs are subject to the release quality criteria. All exemptions from the criteria must be waived by this process and approved by the Bug Waiver Council.

Bug Waiver Council

The Bug Waiver Council consists of the NetBeans p-team members and other team representatives. It's up to the _other_ teams to decide whether they want to have a representative on the council for Netbeans 6.8 or not. Subscribe to nb-bug-waiver-councilATSun.COM in NetAdmin.


An engineer responsible for the bug that requires exemption from the quality criteria is supposed to request a waiver. The following steps are required:

  1. Evaluate the issue in the bug tracking system and provide appropriate justification for the waiver in the issue description
  2. Mark the issue with the 6.9_WAIVER_REQUEST keyword
  3. Send a request to the nb-bug-waiver-councilATSun.COM alias. The request must include the following info:
  • the bug id and a short description
  • the justification for the waiver
  • a statement about user impact (e.g. how often the bug is likely to occur, behavior after the problem occurs, impact on other features, etc.)
  • a workaround description (if available)
  • an estimation when and how the bug will be fixed
  1. Wait 48 hours for any objections from the Bug Waiver Council members. If there are questions/objections, answer/resolve them as appropriate.
    1. If resource scheduling is the reason for waiver request, then the bug council can approve the waiver provided the bug will be addressed in NB 6.8 Patch1. QE should mark the issue with 69fixes1-candidate status-whiteboard value.
  2. If there are no objections within 48 hours (or all of them have been addressed), change the keyword to 6.9_WAIVER_APPROVED. From that moment, the bug is considered waived.
  3. Work with Docs on documenting the waived bug in the release notes (if appropriate)
  4. Discuss within i-team whether the waived bug should be addressed in NB 6.9 Patch1 after 6.9 reaches Code Freeze. If so, QE should mark the issue with 69fixes1-candidate status-whiteboard value.
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo