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
(→Commit Design Decisions) |
(→Commit Design Decisions) |
||
| Line 4: | Line 4: | ||
= Commit Design Decisions = | = Commit Design Decisions = | ||
| − | + | # Identify use cases | |
| − | + | # Idenify all logic that could be implemented as a commit hook | |
| − | + | # Idenitfy all possible conflicts (its.e. relation conflicts) | |
| − | + | # All events must be propogated (i.e. merge) | |
| − | + | # Branching logic on the server side | |
| − | + | # Impacts of removing revert | |
| − | + | # Look into simpler sql where we do processing in the code | |
| − | + | # Regression tests (add, fix, replace) | |
Latest revision as of 15:05, 15 June 2009
Documentation
Commit Design Decisions
- Identify use cases
- Idenify all logic that could be implemented as a commit hook
- Idenitfy all possible conflicts (its.e. relation conflicts)
- All events must be propogated (i.e. merge)
- Branching logic on the server side
- Impacts of removing revert
- Look into simpler sql where we do processing in the code
- Regression tests (add, fix, replace)