Jump to: navigation, search

Virgo/Committers/Process Advice

< Virgo‎ | Committers
Revision as of 12:26, 7 December 2010 by Spowell.vmware.com (Talk | contribs) (First cut)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Development advice for committers

These sections are incomplete. Please either supply the required details or request more information if you require it.

ssh keys; why and how to get them

  • git.eclipse.org
  • build.eclipse.org
  • (other?)

how to fix a bug

All our enhancements and bugs (in fact, every change that happens to the product or the code base) start life with a bugzilla. We generically refer to them all as bugs. Bugzilla entries should record any information associated with the change.

To make it easier to share the work it is helpful to follow some simple guidelines:

  • starting work on a bug
  • giving up on a bug
  • closing a bug

what is a ripple and when to do one


creating a release (milestone or higher)