Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Higgins Development Processes"
m (Added tag for left menu) |
|||
| Line 1: | Line 1: | ||
| − | + | {{#eclipseproject:technology.higgins}} | |
==Developing== | ==Developing== | ||
===Changes to Component Interfaces (APIs)=== | ===Changes to Component Interfaces (APIs)=== | ||
Revision as of 08:00, 16 March 2008
{{#eclipseproject:technology.higgins}}
Contents
Developing
Changes to Component Interfaces (APIs)
- Discuss proposed changes on higgins-dev and gather consensus.
- Locally implement the agreed-upon change (may take days or weeks).
- Announce to higgins-dev that the change is ready.
- Announce that the changes will be checked in on a certain date. Negotiate with others on the date as required.
- Barring any further contention, check in on the agreed-upon date.
Changes to a Component You Don't Own
- 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
- 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