Low: pengine: cl#5056 - Do not allow order dependencies between stonith and non-stonith resources.

There are internal pseudo actions that aggregate the completion
of stonith resources before other resources.  Any attempt to create
an order dependency between a stonith resouce and a non-stonith
resouce has the potential to generate an invalid transition graph.
Because of this, order dependencies between stonith and non-stonith
resouces are now ignored.
Low: pengine: cl#5056 - Regression tests for stonith order constraints
Medium: pengine: cl#5054 - Ensure demote occurs before stop of multistate resource in Master role.

When a native resource's parent is a multistate resource, an order
constraint is set in place to ensure the demote action
of the resource will always occur before the stop action.
This will guarantee that the demote action will always be performed
in the correct order, but it does not guarantee that the demote
action will be performed.  If the demote action is never set to required
it is possible that the stop action will occur without the demote action
entirely.

Right now the demote action will be set to required when we know
the next role of the multistate resource is transitioning from
(Master ---> Slave), or (Master ---> Stopped).  Just because
the next role of the multistate resource does not change, that
does not mean however that the resource will not end up being stopped
by an order constraint later on.  When the multistate resource is stopped
as a result of a order constraint, it is possible that even though the
demote is supposed to happen before the stop action, the demote action
will not be set to required and the resource will transition directly
from Master to Stopped without the demote.

To resolve this, a new order constraint flag has been introduced that
forces the 'first' action to be required when the 'then' action is,
but only when the 'then' action's resource is the Master role.  This
flag is used with the order constraint (demote then stop) to guarantee
that the demote not only occurs in the correct order, but is required
when the Master resource is executing the stop action.
Low: pengine: cl#5054 - Regression tests for demote before stop action for rsc in Master role.
Medium: RA: ClusterMon - Don't fail in stop if the process is missing (bnc#569957)
Low: RA: controld - Fix the typo which should be "globally_unique" (cl#5061, bnc#762603)
Low: Core: Simplify logging initialization helpers for cli tools
High: Core: Support a blackbox for additional logging detail after crashes/errors

The blackbox contains additional debug messages that are not sent to
syslog or logfiles. After a crash or assertion failure, the contents is
written to a separate file, the name of which is recorded in the main
logs.
High: Core: SIGUSR1 now enables blackbox logging, SIGTRAP to write out

This handler is only installed by default for Pacemaker daemons, not
admin tools.
Medium: Core: Allow tracing to be turned on at runtime with SIGPROF
High: Legacy: Fix compilation when building for corosync < 2.0
High: core: Fixes race condition in mainloop add/delete fd wrapper functions.

The g_io_add_watch_full id is never cancelled in mainloop_del_fd().
This means it is possible the mainloop_fd callbacks can be invoked
again after mainloop_del_fd() is executed.
Low: extra: cluster-init - include the ability to sync node times
Low: Convert the last _debug_N logging calls to traces and remove stale macros
High: pengine: Move API additions to avoid ABI incompatabilities
Merge pull request #77 from gao-yan/controld-ra

Low: RA: controld - Fix the typo which should be "globally_unique" (cl#5061, bnc#762603)
High: Core: Revert to the original process flags for the support of rolling-upgrade
Low: RA: ClusterMon - A minor tweak
Build: fix double typedef declarations

Gcc complained about re-declaration of typdefs, even though the header
declarations are with an incomplete struct.
Removing the typedef from the struct definition made gcc happy again.
Build: fix configure --without-corosync