Fixed so that it could change while a setup of "startup-fencing" starts.
Feature: crmd: Set "cluster-name" property to corosync's "cluster_name" by default for corosync-2
Fix: pengine: Use "#cluster-name" in rules for setting cluster-specific instance attributes
Fix: pengine: Use "#site-name" in rules for setting site-specific instance attributes

Node's site-name defaults to cluster-name if unset
Merge pull request #513 from gao-yan/default-cluster-name

Feature: crmd: Set "cluster-name" property to corosync's "cluster_name" by default for corosync-2
Merge pull request #512 from yuusuke/fix_startup-fencing

Fixed so that it could change while a setup of "startup-fencing" starts.
Build: Allow upstream building for i386
Doc: Pacemaker_Explained: Fix options typo
Low: fix small memory leaks
Merge pull request #515 from inouekazu/1.1

Low: fix small memory leaks
Bug rhbz#1097457 - Prevent invalid transition when resource are ordered to start after the container they're started in
Test: PE: Prevent invalid transition when resource are ordered to start after the container they're started in
Bug cl#5212 - Do not promote instances when quorum is lots and no-quorum-policy=freeze
Test: PE: Do not promote instances when quorum is lots and no-quorum-policy=freeze
Merge branch '1.1' of github.com:ClusterLabs/pacemaker into 1.1
Test: cts: allow use of the the 2.0 schema
Bug rhbz#1097457 - Limit the scope of the previous fix and include a helpful comment
Low: cts: more cts changes to allow pacemaker-2.0 schema
Fix: mainloop: Canceling in-flight operations should not fail if child process has already exited.

There's a race condition where we might try and cancel an operation
at the same time it is completing. Depending on the order mainloop
interprets those two conditions the operation might look like it failed
to be canceled, even though the operation's pid has already exited.
Merge pull request #520 from davidvossel/1.1.12-testing2

more cts testing fixes