blob: 2e69b85fc55778773fb6b2ae7dcdc90bd986f8bc [file] [log] [blame]
<HTML>
<HEAD>
<META NAME="NAV_LINK" CONTENT="Guidelines">
<meta name="DESCRIPTION" content="Distribution Structure, API Review Process, AutoUpdate Content Management Process, Release Checklist, Module Writer's Upgrade Guide, Internationalization, Release Process, NetBeans Website Guidelines, NetBeans Board Election Process, Code Conventions, Source Code Commit Rules and Quality-Evangelism">
<TITLE>Guidelines</TITLE>
<link rel="stylesheet" type="text/css" HREF="../../netbeans.css">
</HEAD>
<BODY>
<h1>Guidelines</h1>
<p>NetBeans guidelines are made available to simplify standard
procedures and ensure that all members of the community abide
by them. This is meant to create a uniform way of doing
things with NetBeans and NetBeans.org. Please see the
following topics:</p>
<p><a href="commit.html">Commit Rules</a>:
Committing changes to the NetBeans repository should be done with care - here's
how to check and validate your changes before commiting.
<p><a href="process.html">Release Process</a>:
If you are intested in how new versions of the NetBeans IDE
are released, this is the place. Find information about the
release process, Release Managers, and their responsibilities.</p>
<p><a href="code-conventions.html">Code Conventions</a>:
Formatting, programming practices, and other conventions used in the
NetBeans codebase.
<p><a href="q-evangelism.html">Quality Evangelism</a>:
What are the benefits of writing unit tests and using various tools for finding bugs?
These are the tools that Netbeans developers use for increasing the
quality of our codebase and it's also a summary of reasons why one should write unit tests.
<p><a href="http://bits.netbeans.org/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/i18n-branding.html">i18n</a>:
This document provides recommendations on how to organize the localization and internationalization
(L10n and I18N) of modules in the NetBeans IDE. Other topics
include I18N features, bundle messages, bundle debugging, how
to write better *.properties files, templates, help
documentation, branded localization and more.</p>
<p><a href="au-management.html">AutoUpdate Content Management Process</a>:
A description of the guidelines for managing the content of the
NetBeans AutoUpdate servers - the process for adding and removing
modules.
<p><a href="http://openide.netbeans.org/tutorial/review-steps.html">API Review Process</a>:
A description of the guidelines on reviewing the APIs -
from proposing a change through to implementing it.
<p><a href="https://netbeans.org/download/dev/javadoc/OpenAPIs/org/openide/doc-files/upgrade.html">Module Writer's Upgrade Guide</a>:
A module writer's upgrade guide - API changes you should be aware of,
changes you might need to make to your code, and tips to ensure the
best integration in the latest release.
<p><a href="web-guide.html">NetBeans Project Website Guidelines</a>: Every
netbeans.org project has it's own website, maintained by developers
working on that project. Here's how to make the most of your
website.</p>
<ul>
<li><p><a href="www-guide.html">NetBeans WWW Guidelines</a>: How to commit images,
binaries and HTML pages for documentation or articles. Covers
naming conventions, permissions, formatting, links. </p>
<li><p><a href="css-guide.html">NetBeans CSS Guidelines</a>: The NetBeans stylesheets
has predefined CSS classes that you can use for consistent alignment, tables,
colors, boxes, icons, and borders.</p>
</ul>
<p><a href="../../about/os/election-process.html">NetBeans Board Election Process</a>:
The NetBeans Board consists of two publicly nominated and elected members, and
one Sun-appointed member. Elections are held every 6 months.
</body>
</html>