Enhance the community documentation to spell out the 'trust issues' in Core.
----------------------------------------------------------------------------
Key: QI-275
URL: http://issues.ops4j.org/browse/QI-275
Project: Qi4j
Issue Type: Improvement
Components: Documentation
Affects Versions: 1.2, 1.1, 1.0, 0.7
Reporter: Niclas Hedhman
Assignee: Niclas Hedhman
There are various levels of problems around digging in the Core. There is a
reason why we are fairly restrictive with permissions in the Core, and various
areas are more sensitive than others. For instance, any change that creates (or
may create) data corruption in the entity stores are magnitudes more important
than for instance ensuring that the correct sequence of side effect methods are
invoked, or implementation of Domain Events or Aggregates which are large new
features, hard to get right, but can rely more on existing test suite to ensure
nothing breaks.
For instance; I would like to add a section of the community contract that ANY
CHANGE to an existing test case (in Core) to be discussed and reviewed before
being made.
If you have any further suggestions, list below in Comments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
