OSEE/Define/Developers Guide
< OSEE
Revision as of 14:05, 15 June 2009 by Megumi.telles.boeing.com (Talk | contribs) (→Commit Design Decisions)
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)