WaiverProcess

(Difference between revisions)
(Process)
(NetBeans 6.9 Bug Waiver Process)
Line 1: Line 1:
__NOTOC__
__NOTOC__
-
===NetBeans 6.9 Bug Waiver Process===
+
===NetBeans 7.0 Bug Waiver Process===
-
* Issuezilla Keywords for NetBeans 6.9
+
* Issuezilla Keywords for NetBeans 7.0
-
:*'''6.9_WAIVER_REQUEST''' - when asking for waiver ([http://www.netbeans.org/issues/buglist.cgi?keywords=6.9_WAIVER_REQUEST issues])
+
:*'''7.0_WAIVER_REQUEST''' - when asking for waiver ([http://www.netbeans.org/issues/buglist.cgi?keywords=7.0_WAIVER_REQUEST issues])
-
:*'''6.9_WAIVER_APPROVED''' - when waiver was approved by team ([http://www.netbeans.org/issues/buglist.cgi?keywords=6.9_WAIVER_APPROVED issues])
+
:*'''7.0_WAIVER_APPROVED''' - when waiver was approved by team ([http://www.netbeans.org/issues/buglist.cgi?keywords=7.0_WAIVER_APPROVED issues])
====Purpose====
====Purpose====
-
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'''.
+
High-priority bugs are subject to the release quality criteria. All exceptions must be waived by this process.  
-
 
+
-
====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-council''AT''Sun.COM in NetAdmin.
+
====Process====
====Process====
-
An engineer responsible for the bug that requires exemption from the quality criteria is supposed to request a waiver. The following steps are required:
+
An engineer responsible for the waived bug is supposed to request a waiver :
-
# Evaluate the issue in the bug tracking system and provide appropriate justification for the waiver in the issue description
+
# Add appropriate justification for the waiver in the issue description
-
# Mark the issue with the '''6.9_WAIVER_REQUEST''' keyword  
+
# Mark the issue with the '''7.0_WAIVER_REQUEST''' keyword  
-
# Send a request to the '''nb-bug-waiver-council''AT''Sun.COM''' alias. The request must include the following info:
+
# Send a request to the '''nbdev''AT''netbeans.org''' alias. The request must include the following info:
:* the bug id and a short description
:* the bug id and a short description
:* the justification for the waiver
:* 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 statement about user impact (e.g. how often the bug is likely to occur, behaviour after the problem occurs, impact on other features, etc.)
:* a workaround description (if available)
:* a workaround description (if available)
:* an estimation when and how the bug will be fixed
:* an estimation when and how the bug will be fixed
-
# Wait 48 hours for any objections from the Bug Waiver Council members. If there are questions/objections, answer/resolve them as appropriate (if resource scheduling is the reason for waiver request, then the bug council can approve the waiver provided the bug will be addressed in Patch1 - mark the issue with '''69fixes1-candidate''' status-whiteboard value).
+
# Wait 48 hours for any objections :
-
# 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.
+
:*If there are questions/objections, answer/resolve them as appropriate
 +
:*No objections (or all of them have been addressed), change the keyword to '''7.0_WAIVER_APPROVED'''.
# Work with Docs on documenting the waived bug in the release notes (if appropriate)
# Work with Docs on documenting the waived bug in the release notes (if appropriate)
-
# Discuss within i-team whether the waived bug should be addressed in NB 6.9 Patch1 after 6.9 reaches Code Freeze. If so, mark the issue with 69fixes1-candidate status-whiteboard value.
+
# If scheduling is an issue to address issue in current release, it should be addressed in a Patch. If so, mark the issue with status-whiteboard '''70patch-candidate''' value.

Revision as of 17:01, 10 November 2010

NetBeans 7.0 Bug Waiver Process

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

Purpose

High-priority bugs are subject to the release quality criteria. All exceptions must be waived by this process.

Process

An engineer responsible for the waived bug is supposed to request a waiver :

  1. Add appropriate justification for the waiver in the issue description
  2. Mark the issue with the 7.0_WAIVER_REQUEST keyword
  3. Send a request to the nbdevATnetbeans.org 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, behaviour 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 :
  • If there are questions/objections, answer/resolve them as appropriate
  • No objections (or all of them have been addressed), change the keyword to 7.0_WAIVER_APPROVED.
  1. Work with Docs on documenting the waived bug in the release notes (if appropriate)
  2. If scheduling is an issue to address issue in current release, it should be addressed in a Patch. If so, mark the issue with status-whiteboard 70patch-candidate 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