Revision as of 09:49, 20 October 2016 by Jkovalsky (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

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

NetBeans 8.2 Patch 1
Used Whiteboard 82patch1-candidate
Scheduled for 2016-12-15
Bugs nomination cut-off 2016-12-5
Code Freeze (all bug fixes backported to release82 branch) 2016-12-9
Update scenarios tested, Go/NoGo 2016-12-14
NetBeans 8.2 Patch 1 available on Update Center 2016-12-15
Links to BugZilla
82patch-candidate(s) 1
82patch1-candidate(s) 2
82patch1-fixed 3
82patch1-candidate & VERIFIED 4
82patch1-verified 5
P1/2s fixed in trunk since last CF date 6
82patch1-candidates not yet verified 7

How to nominate issues

  • Bugs nomination (Anybody) : add 82patch-candidate into Whiteboard (SW) field in BugZilla (Potential candidates [query 1])
  • Coordination (Coordinator) : chooses and approves candidates to be integrated into the next patch (change SW to 82patch1-candidate [query 2])

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 release82 branch in repository releases, details: HgHowTos#Working_with_release_branches
    • 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 82patch1-candidate to 82patch1-fixed and set Target Milestone accordingly (e.g. from "8.2" to "8.2.1" if "8.2.1" is available)

How to verify and test (QE)

  1. Pre-integration testing: verify fixes of issues with SW 82patch1-candidate in trunk (change status to VERIFIED [query 4])
  2. Issues verification:
    • verify fixes in the build from releases/release82 branch
    • change SW for appropriate issue from 82patch1-fixed [query 3] to 82patch1-verified [query 5]
  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 NetBeans8.2PatchesInfo 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