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

Difference between revisions of "Higgins Development Processes"

(New page: ===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 ...)
 
(Links)
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
 +
[[Image:Higgins_logo_76Wx100H.jpg|right]]
 +
==Developing==
 
===Changes to Component Interfaces (APIs)===
 
===Changes to Component Interfaces (APIs)===
# Discuss proposed changes on higgins-dev and gather consensus
+
# Discuss proposed changes on higgins-dev and gather consensus.
 
# Locally implement the agreed-upon change (may take days or weeks).
 
# Locally implement the agreed-upon change (may take days or weeks).
# Announce that the change is ready and will be checked in on a certain date. Negotiate with others on the date
+
# Announce to higgins-dev that the change is ready.
# If changes are required in [[Components]] other than one you own, then email the owner(s) and cc higgins-dev the set of diffs
+
# Announce that the changes will be checked in on a certain date. Negotiate with others on the date as required.
# Wait for approval from the owner(s)
+
 
# Barring any further contention, check in on the agreed-upon date.
 
# 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===
 
===Announcements of Significant Changes===
 
* Committers should post to higgins-dev when they make changes of general interest to other Higgins committers
 
* Committers should post to higgins-dev when they make changes of general interest to other Higgins committers

Latest revision as of 10:53, 30 July 2009

{{#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

Back to the top