60Beta1QC

NetBeans 6.0 Beta 1 Fixing and Waiving

This page defines NetBeans 6.0 Beta 1 release process

Important Beta 1 abbreviations

Beta 1 branch release60_beta1
Waiver keyword 6.0_BETA1_WAIVER
Stopper fixed Status whiteboard beta1fix


All P1s have to be fixed for Beta 1 (based on Beta 1 Quality Criteria). We also need to meet P2s bug count criteria - 200/400 (target/boundary).

  • Cut off date for P2s bug counts (counted for reaching Open P2s boundary purpose) is Thu 30 Aug, 9am PDT
  • Cut off date bug counts, see attachements: By Team & By Component
  • Fixing countinues after this date on full speed.

High Resistance

In order to better stabilize 6.0 Beta 1 we will utilize High Resistance process. Only stoppers can be fixed at High Resistance.

  1. HR starts on Mon, Sep 3rd 8:00am CET time in trunk.
  2. Beta 1 release60_beta1 branch is created on Mon, Sep 3rd 8:00am-12:00am CET. This branch is used only for HR integrations.
    1. When Beta 1 branch is created trunk is opened for any integrations.
  3. Daily build is done from Beta 1 branch.
  4. Beta 1 fixes are only stoppers (P1) selected by QE.
  5. Status whiteboard beta1fix (issues) will be used to mark bugs fixed for Beta 1 branch
  6. Bug to be fixed during HR has to be sent to reviewersATnetbeans.org with description
  7. Bug is integrated into release60_beta1 branch. (commits)
  8. P2s are evaluated for showstopper status as usuall

Fixing of all priorities continues in trunk.

Beta1 Waiver

P1s those are considered to have a low impact on users will be marked with keyword 6.0_BETA1_WAIVER (issues). Following steps are required:

  1. Evaluate the issue in IssueZilla and provide appropriate justification for the waiver in the issue description
  2. Send a request to the nb-bug-waiver-councilATsun.com alias and include following info:
    1. bug id and a short description
    2. justification for the waiver
    3. statement about user impact (e.g. how often the bug is likely to occur, behavior after the problem occurs, impact on other features, etc.)
    4. workaround description (if available)
    5. estimation when and how the bug will be fixed
  3. Wait 24 hours for any objections. If there are questions/objections, answer/resolve them as appropriate.
  4. If there are no objections within 24 hours (or all of them have been addressed), set the keyword to 6.0_BETA1_WAIVER. From that moment, the bug is considered waived.



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