Revision as of 18:11, 8 February 2012 by Jglick (Talk | contribs)

This page documents the process and responsibilities in patches to NetBeans releases.

How to nominate issues

  • Bugs nomination (Anybody) : add 71patch-candidate into Status Whiteboard (SW) field in BugZilla
  • Coordination (Coordinator) : chooses and approves candidates to be integrated into the next patch (change SW to 71patch1-candidate)

How to proceed with patch (Developers)

  1. wait until patch candidate is VERIFIED in trunk (if doesn't happen for long time please notify your QE or Coordinator)
  2. Issues integration:
    • you can use hg graft or hg transplant to cherry-pick a bug fix from default branch into release71_fixes branch in repository releases, details: HgHowTos#WorkingWithReleaseClones
    • Increasing spec. version numbers:
      • increase the third version number by 1 (X.Y.Z -> X.Y.Z+1) of all patched modules (DO NOT for org.netbeans.modules.reglib, org.netbeans.modules.updatecenters)
      • add following text into Long Description : For the list of included fixed bugs please check
    • change SW of appropriate issue from 71patch1-candidate to 71patch1-fixed and set Target Milestone accordingly (e.g. "7.1.1")

How to verify and test (QE)

  1. Pre-integration testing: verify fixes of issues with SW=71patch1-candidate in trunk (change status to VERIFIED)
  2. Issues verification:
  3. Regression testing
  4. Download/Installation testing: test all scenarios covering to installation/patching already released bits+patches

How to release patch (Coordinator, BE)

  1. Update NetBeans7.1PatchesInfo page (Coordinator): provide list of fixed issues and list of patched plugins & related version numbers
  2. Publishing patch (BE): published patch on live UC
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