NetBeans 6.5 Code Freeze Process

In order to better stabilize 6.5 FCS we will utilize Code Freeze process. Only stoppers can be fixed at Code Freeze.

  • CF starts on Sep 13 8:00am CET time in main.
  • 6.5 release65 clone is created on Oct 13 8:00am-12:00am CET. This clone is used only for CF integrations. Creator of clone should read HgCreatingReleaseClones.
  • When release65 clone is created main is opened for post 6.5 integrations.
  • Build from release65 clone is done on daily basis till RC1 then on demand
  • release65 fixes are only stoppers (P1s) selected by QE or ML fixes
  • Bug must be first integrated in main and verified by QE
  • Bug to be fixed in release65 during CF must be sent to reviewersATnetbeans.org and must contain the following information:
  • Description of the bug (including IZ #)
  • Impact assessment i.e. why it is a showstopper?
  • Risk assessment i.e. why is it safe?
  • Confirmation of peer code review and QE verification of fix
  • Changeset info (for reviewing diffs)
  • Mark the bug with 65_HR_FIX keyword
  • Bug is integrated into release65 clone. (commits)
 You can use hg transplant to cherrypick a bug fix from main into release65.  How to
  • P2s are evaluated for showstopper status as usual

Fixing of all priorities continues in trunk.

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