Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[aperi-dev] Extending Aperi: summary of steps:

When planning a change or addition to an Aperi component through an extension/plugin, what does an open source user need to keep in mind? I am looking for a high-level summary of steps, similar to something like this:

1. Analyze the impact of the changes on the whole of Aperi.
2. Submit a change request to the component design team.
3. Test the change or addition by make an overall build with all the changes to ensure nothing breaks.
4. Send out a note to the aperi-dev mailing list highlighting the change.

Can anyone add to this list or suggest edits?
_________________

Chris King
Aperi information development
External: 512.687.5166
IBM: 273.5547
chriskng@xxxxxxxxxx
Aperi: http://www.eclipse.org/aperi/index.php

Back to the top