UpdateCenterProcess

Contents

Process of NetBeans Plugins Publishing on the NetBeans Update Center

This document describes a way how NetBeans plugin developers can get their plugins published on the NetBeans Update Center. The process is very easy and valid for contributions that originated in both NetBeans community and Oracle company. Note: This process is valid for plugins working with NetBeans IDE 6.9 and older. Plugins working with NetBeans IDE 7.0 and newer should be published on the Plugin Portal and then request publishing on the Plugin Portal Update Center.

Process visualisation

Image:auc_process_small_UpdateCenterProcess.png

  1. Contributor submits request to publish a plugin on the NetBeans Update Center (UC) through Request Form
  2. Request is filed as a new TASK in Bugzilla against updatecenters product and component based on user's choice (Third-party|Dev|Beta|Stable)
  3. NetBeans Release Boss (RB) being a default owner of updatecenters product is notified by e-mail.
  4. RB reviews the UC request (especially legal and quality readiness) and approves/rejects publishing the plugin on selected UC by adding a comment to the issue.
  5. Contributor is responsible for sanity testing (*) the plugin before it's published.
    1. There are no particular quality requirements for Alpha quality plugins.
    2. Beta quality plugin is published if contributor confirms it does not contain any P1 defects.
    3. Stable quality plugin is published if contributor confirms it does not contain any P1 or P2 defects and i18n support is implemented.
    4. Third-party plugin is published if contributor confirms it does not contain any P1 or P2 defects.
  6. Build Engineering publishes module on selected UC.
  7. Release Boss updates content plan (for example [5]) for the appropriate UC.

(*) Verification of smooth installation and very basic functionality test to be sure that IDE is not seriously broken.

Plugin publishing

Anyone registered at netbeans.org [1] can publish own NetBeans plugin on Update Center. In order to get it there, plugin contributor must submit official request [2] via a simple web form. Please get familiar with our plugin quality criteria [3].

Plugin update/removal

Whenever contributor wants to update/remove already published plugin (e.g. due to a bug fix), s/he must create a TASK issue against updatecenters product and appropriate component [4] in Bugzilla. All the necessary information should be mentioned in the description field.

Plugin renewal

When new "dot" version of NetBeans is planned, Release Boss creates UC content plans (similar to e.g. 6.9 Stable UC plan [5]) and contacts 1 week prior to Feature Freeze all plugin contributors with request to check compatibility of their plugins with the new release. If they confirm the plugin works with new NetBeans version, the plugin is added into the list of plugins planned to be available for end users.

Bugs in UC hosted plugin

  • All UC requests are tracked as TASKs in Bugzilla.
  • If bug is found in UC hosted plugin, it is reported against updatecenters product and appropriate component depending on the UC type where the plugin is hosted.
  • Such bug is assigned to plugin contributor.
  • In case of P1/P2 bugs contributor is asked to fix it soon otherwise plugin could be removed from our UC.
  • If bug is not appropriately resolved, plugin is removed from UC or downgraded (Stable -> Beta, Beta -> Dev).

[1] https://netbeans.org/people/signup
[2] http://netbeans.org/community/guidelines/au-request-form.html
[3] http://wiki.netbeans.org/PluginPortalQualityCriteria
[4] https://netbeans.org/bugzilla/enter_bug.cgi?product=updatecenters&cf_bug_type=TASK
[5] http://wiki.netbeans.org/NB69StableModulesUC

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