Update Centers Concept for NetBeans 6.0

NetBeans 6.0 users will be able to get standard features from within the IDE. For example they can install only Java support and still are able later add Ruby support or UML via using the redesigned plugin manager. No need to re-run the installer. The new auto update client also has the ability to pull software which is not a standard NetBeans module from the Update Center (UC). This could be used to deliver runtimes such as Wireless Toolkits. Application servers like GlassFish will not be available on the UC and users will be encouraged to download them, install and register in the IDE manually.

NetBeans 6.0 (Beta 2, RCx and FCS) will have the following UCs. The development UC will be only included with development builds. The names are final. Both the NBM files and module catalogues will be physically located on dlc.sun.com under /netbeans/updates/6.0/uc/ [beta2/thirdparty| [stable/catalog.xml.gz. The URLs will point to updates.netbeans.org instead of the dlc.sun.com. Plugin Portal UC will be http://plugins.netbeans.org/nbpluginportal/updates/6.0/catalog.xml.gz.

  • NetBeans - All plugins that are either part of the full NetBeans distro or additional features. The content of this UC is result of the normal NetBeans build plus patched version of broken modules plus manually published stable quality plugins. This UC will replace original HotFixes UC as well.
  • NetBeans Beta - Beta quality plugins certified by NetBeans. This UC will be turned on since NetBeans 6.0 Beta 2. Planned content is available here.
  • 3rd Party Plugins - Free versions of commercial plugins certified by NetBeans. This UC will be turned on.
  • Plugin Portal - Plugins from Plugin Portal that were reviewed and approved to show up on this UC. This UC will be turned on in NetBeans 6.0 but it will remain empty until action plan is succesfully implemented.

Delivering patches

If there is a need to provide an update of module (serious bug fix) the following steps need to be done:

  1. Responsible developer commits the fix to trunk (ideal but not mandatory)
  2. Quality Assurance engineer is found who will verify patched functionality
  3. Sustaining lead is notified (via product team in ideal case)
  4. Patch schedule is prepared by Sustaining with input and approval from Quality Engineering and Release Engineering teams
  5. Bug fix is integrated into appropriate patch branch and specification version is increased by Sustaining team
  6. Changed bundle files are translated by L10N team
  7. Release Engineering team builds patched NBM file
  8. Unit testing is done by Sustaining team
  9. Functional testing is done by Quality Assurance engineer
  10. L10N team verifies translation changes
  11. Sustaining team creates new AUC request by way of AutoUpdateProcess and provides patched NBM file to AUC coordinator
  12. Patched module is staged on NetBeans UC
  13. Staged module is verified by responsible Quality Assurance engineer and gives a Go
  14. Patched module is made live by Release Engineering team
  15. Sustaining team releases the patch on SunSolve and completes the process
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