Difference between revisions of "Architecture Council/Things Committers Should Know"

From Eclipsepedia

Jump to: navigation, search
Line 1: Line 1:
On a bi-weekly basis, the [[Architecture Council]] sends a short note out to Eclipse Committers (via the committers mailing list) describing some aspect of the [http://www.eclipse.org/projects/dev_process/development_process.php Eclipse Development Process]. The idea is to provide very short (i.e. one paragraph) reminders of important information  in a form that committers are able to quickly digest. This page serves as an archive for these notices. Future notices are under development on the [[Architecture Council/Things Committers Should Know Staging | staging]] page.
+
On a bi-weekly basis, the [[Architecture Council]] sends a short note out to Eclipse Committers (via the committers mailing list) describing some aspect of the [http://www.eclipse.org/projects/dev_process/development_process.php Eclipse Development Process]. The idea is to provide very short (i.e. one paragraph) reminders of important information  in a form that committers are able to quickly digest. This page serves as an archive for these notices. Future notices are under development on the [[Architecture Council/Things Committers Should Know/Staging | staging]] page.
  
 
We've only just started this effort; the archive is currently empty.
 
We've only just started this effort; the archive is currently empty.

Revision as of 16:37, 13 November 2008

On a bi-weekly basis, the Architecture Council sends a short note out to Eclipse Committers (via the committers mailing list) describing some aspect of the Eclipse Development Process. The idea is to provide very short (i.e. one paragraph) reminders of important information in a form that committers are able to quickly digest. This page serves as an archive for these notices. Future notices are under development on the staging page.

We've only just started this effort; the archive is currently empty.