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 "OSEE/Define/Developers Guide"
< OSEE
(→Documentation) |
(→Commit Design Decisions) |
||
| Line 3: | Line 3: | ||
= Commit Design Decisions = | = Commit Design Decisions = | ||
| + | |||
| + | 1. Identify use cases | ||
| + | 2. Idenify all logic that could be implemented as a commit hook | ||
| + | 3. Idenitfy all possible conflicts (its.e. relation conflicts) | ||
| + | 4. All events must be propogated (i.e. merge) | ||
| + | 5. Branching logic on the server side | ||
| + | 6. Impacts of removing revert | ||
| + | 7. looking into simpler sql where we do processing in the code | ||
| + | 8. Regression tests (add, fix, replace) | ||
Revision as of 15:05, 15 June 2009
Documentation
Commit Design Decisions
1. Identify use cases 2. Idenify all logic that could be implemented as a commit hook 3. Idenitfy all possible conflicts (its.e. relation conflicts) 4. All events must be propogated (i.e. merge) 5. Branching logic on the server side 6. Impacts of removing revert 7. looking into simpler sql where we do processing in the code 8. Regression tests (add, fix, replace)