[ https://issues.jboss.org/browse/OVERLORD-144?page=com.atlassian.jira.plug... ] Gary Brown commented on OVERLORD-144: ------------------------------------- I think the main argument is, for governance to be effective it must be outside the control of the development organisation, but at the same time not become a burden on them in such a way that it would impact their work. Therefore, development organisation would use CI in support of doing their own development work, running unit and integration tests to ensure they can regressions at the earliest possible time in the development lifecycle, to avoid the issues being detected later in the lifecycle (i.e. by QE), which would increase the cost of fixing the problem considerably. For the same reason, applying governance policies at the earliest possible stage in the development lifecycle reduces the cost of detecting any issues. For example, if a WSDL definition is found to no comply to WS-I during development, it is relatively inexpensive to fix. If the problem is only detected after the system is released, then it is more time consuming to fix. Having governance externalised means that organisations don't have to rely on the development team and their supporting infrastructure to correctly apply the governance policies. It also means the organisation has flexibility to change those policies (or introduce new ones) without impacting the development infrastructure/team. -- This message was sent by Atlassian JIRA (v6.2.6#6264)