fix http://stackoverflow.com/questions/4826639/repack-of-git-repository-fails
plugins/routing/activemq: s/TOPIC/DESTINATION/

In the ActiveMQ routing plug-in, change the ACTIVEMQ_TOPIC setting to be
ACTIVEMQ_DESTINATION as the value may be either a topic or a queue.

For compatibility, ACTIVEMQ_TOPIC is used if ACTIVEMQ_DESTINATION is not
specified.

This commit fixes bug 1110454.
Fix unclear variable name
Update oo-install portable installer links
feat(fog_plugin): implement fog plugin
tests(fog_plugin): fog plugin unit tests
fix bug 1122339
https://bugzilla.redhat.com/show_bug.cgi?id=1122339
add detection to make sure node_platform is not nil before casecmp
util-scl/oo-mco: Added error message when scl mco does not exist.

Bug 1131139
Bugzilla link https://bugzilla.redhat.com/show_bug.cgi?id=1131139
oo-mco is installed on nodes due to rpm configuration, however the scl mco executable is not. Added error message to avoid confusion for newer administrators.
Bug 1123988 - Added scipy for python-2.7 and python-3.3 cartridges
Fix websockets in jbossas cartridge

Remove WebSocket-* lines from jbossas cartridge manifest, as nothing is
currently using them. Their existence causes the node web proxy to try
to route websocket connections to port 8676, which isn't being used.

Bug 1133823
update version string to match convention
Automatic commit of package [rubygem-openshift-origin-gear-placement] release [0.0.2-1].
Fixing has_app_cartridge method
Created a multi writer option which logs to both syslog and files
Don't want to aggregate bytes here, just returning len(b) for failed writer
Close all writers before returning error. Also fixed bug in last commit
Changed error handling in various places.
move xpaas cucumber tests upstream
Bug 1131031 - improving /etc/group, /etc/shadow recovery
broker: ensure normalization is idempotent

https://bugzilla.redhat.com/show_bug.cgi?id=1131317
Bug 1131317 - Fail to run 'rhc setup' when normalizing user with complex matrix on broker

When the username is normalized, then stored, then retrieved and used in
a new request, it is normalized again. In order for this to match,
normalization should be idempotent. It's possible to come up with
reasonable normalizations that accidentally break this rule. So, to make
sure, we now normalize names repeatedly until the answer stays the same.