Feature: pengine: cl#5174 - Allow resource sets and templates for location constraints
Test: pengine: cl#5174 - Allow resource sets and templates for location constraints
Feature: crm_ticket: Support multiple modifications for a ticket in an atomic operation

Other change:
Grant and revocation of tickets are allowed only if --force is supplied.
Low: crmd: Change the default value of node-action-limit
Merge pull request #407 from inouekazu/default_node-action-limit

Low: crmd: Change the default value of node-action-limit
Merge pull request #403 from gao-yan/crm_ticket-atomic-op

Feature: crm_ticket: Support multiple modifications for a ticket in an atomic operation
Fix: services: Fixes segfault associated with cancelling in-flight recurring operations.

Many thanks to Kazunori INOUE for both identifying the
issue and diligently tracking down the source of the problem.
Test: tools: Update the regression tests of crm_ticket
Merge pull request #409 from gao-yan/crm_ticket-tests

Test: tools: Update the regression tests of crm_ticket
Merge pull request #399 from gao-yan/location-sets-templates

 Feature: pengine: cl#5174 - Allow resource sets and templates for location constraints
Merge pull request #408 from davidvossel/fix_action_cancel_crash

Fix: services: Fixes segfault associated with cancelling in-flight recurring operations
Fix: upstart: Allow comilation with glib versions older than 2.28
Fix: Make coverity happy
Fix: crmd: Prevent memory leak in error paths
Fix: Prevent potential use-of-NULL
Fix: stonith_admin: Ensure pointers passed to sscanf() are properly initialized
Doc: Clusters From Scratch: Fix image sizes in PDF output
Log: PE: Downgrade message showing detected masters
High: cl#5055: Improved migration support.

Migrations are now calculated in a way that allows
them to be executed in much more complex situations.
Low: updated pengine regression tests for improved migration support

Why these changes are okay.

Improved migrate logic allows migration in this scenario when it
previously was not about to be calculated.
- bug-1820-1
- bug-1820

Groups are allowed to migrate now
- group-dependants

Clone child instance ordering is preserved even though
the pseudo action ordering has shifted.
- migrate-5.summary
- migrate-both-vms
- migrate-stop-complex
- migrate-stop
- order-serialize-set
- order-serialize

Advisory ordering between a clone and a migrating primitive.
During a migration, the stop action of the migration does not
have advisory ordering enforced.  During a migration, the resource
never actually stops. If this was a manditory ordering, the migration
would not happen.
- migrate-stop_start
- novell-252693-3
- novell-252693

The original migration was allowed incorrectly. The partial
migration target changed during the next calcuation, resulting
in the migration needing to be aborted.  The new migration
logic handles this correctly.
- migrate-partial-4

Order constraints where A then B, If A is migrating, B
does not have to stop anymore.
- migrate-stop-start-complex
- bug-1820-1