(Difference between revisions)
(Current patch (NetBeans 6.8 Patch 1) :)
(Current patch (NetBeans 6.8 Patch 1) :)
Line 5: Line 5:
* ''Status Whiteboard'' : [ 68patch-candidate]
* ''Status Whiteboard'' : [ 68patch-candidate]
* ''Clone'' : [ release68_fixes] for IDE; [ branch release68_fixes] for Java FX
* ''Clone'' : [ release68_fixes] for IDE; [ branch release68_fixes] for Java FX
* Schedule :
* Schedule :
:* '''20/January''' - Nomination cut-off date
:* '''20/January''' - Nomination cut-off date

Revision as of 22:43, 28 January 2010

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

Current patch (NetBeans 6.8 Patch 1) :

  • 20/January - Nomination cut-off date
  • 25/January - Code Freeze
  • 26/January - 29/February - Functional Testing
  • 1/February - 4/February - Installation testing
  • 5/February - Patch released

How to nominate issues

  • Bugs nomination (Anybody) : using Status Whiteboard (SW) field in BugZilla:[VERSION]patch-candidate should be added to the SW (e.g, 68patch-candidate)
  • Coordination (Coordinator) is responsible for the whole process : nomination/selection of issues/pre-integration testing/integration/verification/regression testing/publishing patch/download testing/announcement
    may be anybody (Sustaining/QE coordinate patches once a month(if needed) for any version of NetBeans)

How to proceed with patch

  1. Issues selection (Coordinator): go through issues with SW=[VERSION]patch-candidate and change it for selected issues to [VERSION]patch[NUMBER_OF_PATCH]-candidate
  2. Pre-integration testing (Coordinator/QE): verify fixes of issues with SW=[VERSION]patch[NUMBER_OF_PATCH]-candidate in the trunk
  3. Issues integration (Coordinator/Developer):
    • you can use hg transplant to cherry-pick a bug fix from team repository into release[VERSION]_fixes clone, details: HgHowTos#WorkingWithReleaseClones
    • change SW for appropriate issue from [VERSION]patch[NUMBER_OF_PATCH]-candidate to [VERSION]patch[NUMBER_OF_PATCH]-fixed
  4. Increasing spec. version numbers (Coordinator):
    • increase the third version number by 1 (X.Y.Z -> X.Y.Z+1)
    • Increase spec. versions of all modules on the chain till visible kits/plugins you would like to tight the patch with!
    • add following text into Long Description : For the list of included fixed bugs please check[VERSION]PatchesInfo.
    • don't increase for : org.netbeans.modules.reglib, org.netbeans.modules.updatecenters
  5. Issues verification (Coordinator/QE):
    • verify fixes in the build from release[VERSION]_fixes clone
    • change SW for appropriate issue from [VERSION]patch[NUMBER_OF_PATCH]-fixed to [VERSION]patch[NUMBER_OF_PATCH]-verified
  6. Regression testing (Coordinator/QE):
  7. Request to publish patch (Coordinator): report an issue against auc/stable (e.g. 6.5 Patch 2)(publishing itself covered by Build Engineering)
  8. Download/Installation testing (Coordinator/QE): test all scenarios covering to installation/patching already released bits+patches (QE used to run all-pairs testing ... e.g. NetBeans651InstallerTesting)
  9. Update NetBeans[VERSION]PatchesInfo page (Coordinator): provide fixed Issue Id, Issue Description, release date, List of patched plugins & related version numbers (e.g. NetBeans6.5PatchesInfo)
  10. Publishing patch (Build Engineering): published patch on live UC
  11. Update Sun Solve (Sustaining): once a month update all not yet uploaded modules to Sun Solve

General Links on issues, and patch info:

NetBeans Patches - Released

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