Jump to: navigation, search

Higgins Development Processes

Revision as of 10:53, 30 July 2009 by Ptrevithick.gmail.com (Talk | contribs)

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

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

Developing

Changes to Component Interfaces (APIs)

  1. Discuss proposed changes on higgins-dev and gather consensus.
  2. Locally implement the agreed-upon change (may take days or weeks).
  3. Announce to higgins-dev that the change is ready.
  4. Announce that the changes will be checked in on a certain date. Negotiate with others on the date as required.
  5. Barring any further contention, check in on the agreed-upon date.

Changes to a Component You Don't Own

  1. If changes are required in Components other than one you own, you must email the owner(s) the set of attached diffs cc--ing higgins-dev
  2. Wait for approval from the owner(s) before checking in

Announcements of Significant Changes

  • Committers should post to higgins-dev when they make changes of general interest to other Higgins committers