cornercorner
FeaturesPluginsDocs & SupportCommunityPartners

NB67HighResistance

NetBeans 6.7 High Resistance


In order to better stabilize 6.7 FCS we will utilize HR process.

Dates :

  • HR starts on May 22 8:00pm CEST time in main-silver - means all team repositories are closed until announcement is sent.
  • The only exception is CND team, which can follow up with integrations up to May 23 2am CEST and only into cnd-main repository
  • Clone is created on May 22 / May 23. Announcement email is sent and team repositories are opened for integrations, once the clone is ready to be used.

Process :

  1. integrate fix (into team repository/silver) -> leave issue as STARTED with TM=6.7
  2. verify fix by QE (build from team repository or silver/golden) -> add comment into the issue
  3. review fix by peer -> add comment into the issue
  4. sent an email to reviewersATnetbeans.org with following informations:
  • 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)
  1. integrate fix into release67 clone and mark issue with 67_HR_FIX keyword -> change issue to RESOLVED FIXED and add 67_HR_FIX keyword
    1. you can use hg transplant to cherry-pick a bug fix from team repository into clone
    2. or if the parent revision was in the clone, you can just pull & merge it
    3. details: HgHowTos#WorkingWithReleaseClones


Terms :

  • All P2s are evaluated for showstopper status
  • HR fixes are only stoppers (P1s) selected by QE
  • HR starts at time clone is created
  • Clone is used only for HR integrations
  • When clone is created all repositories are opened for integrations.
  • Builds from clone are done on demand


Fixing of all priorities continues in trunk.

Retrieved from "http://wiki.netbeans.org/NB67HighResistance"