Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Higgins Development Processes

Revision as of 13:46, 22 March 2007 by Unnamed Poltroon (Talk) (Changes to Component Interfaces (APIs))

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 that the change is ready
  4. If changes are required in Components other than one you own, then email the owner(s) and cc higgins-dev the set of diffs
  5. Wait for approval from the owner(s)
  6. Announce that the changes will be checked in on a certain date. Negotiate with others on the date as required.
  7. Barring any further contention, check in on the agreed-upon date.

Announcements of Significant Changes

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

Back to the top