NewCommittersGuide

This guide aims to introduce new NetBeans committers to the policies and procedures used by the NetBeans developer community. It needs to grow quite a bit to cover all the important aspects of our development process. However the information here should be up-to-date and accurate.

Inter-Module and Inter-Cluster Dependencies

Developers should not make API changes or add or remove modules among the stable NetBeans modules without going through the API review process. Some dependencies are simply not allowed; for example, Ruby or C/C++ support must never have a hard dependency on Java support cluster. These kinds of changes are detected automatically by the continuous build process and notifications are sent to the api-changes@netbeans.org mailing list.

API Changes in Non-Private Packages

Developers should not make API changes or add or remove modules among the stable NetBeans modules without going through the API review process. The changes in signatures of public and friend packages of all modules are detected by SignatureTest build running on the continuous build process and notifications are sent to the api-changes@netbeans.org mailing list.


All technical leads should subscribe to this list and should review all the changes to make sure they were made according to the outcome of the API review. Mistakes must be corrected immediately because usually they are expensive to fix later, sometimes even impossible if they leak into the final releases because we place a premium on backward compatibility.

As a new committer you should always seek advice and reviews from the technical leads in your area before attempting to do this kind of change.

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