Low: build: Ability to build separate docs based on different cli types (pcs or crm)
Low: Build: Place coverage results in the current directory
High: Fencing: Once again record the node's uname when connecting to the cluster (prevents use-of-NULL)
Low: cts: Update help text
Low: services: Keep the compiler happy when upstart and systemd are not supported
High: ipc: Correctly detect old replies
Low: Core: All logs are sent to the Blackbox if enabled
Low: Core: Better ipc trace logging
Low: Core: Trial a 5Mb blackbox buffer
Low: crmd: Reduced logging format for incomplete transtions
Low: Core: Improved ipc trace logs
High: mcp: Do not shut down IPC until the last client exits

When running on top of cman or the v1 plugin, doing so causes client
connections to be dropped and the clients to exit ungracefully.
Low: Core: Simplify blackbox handling now that all messages go there if it is enabled
Low: cts: New stonith patterns
High: legacy: Correctly update node status when using the corosync plugin
High: crmd: Correctly handle scheduled node down events
High: fencing: cl#5092 - Always timeout stonith operations if timeout period expires.

When a stonith operation's timeout period is reached, stonithd sends
the child process SIGTERM and then SIGKILL if the process is still around.
Later on the WIFSIGNALED macro is used to determine if the process was
sent one of these two signals. The problem with that macro is that it will
only return the signal if the child process ignored it.  If a process detects
the SIGTERM signal and exists, WIFSIGNALED returns nothing so we don't
report the timeout occurred.

Now if the operation timer expires, stonith treats that operation as being
timed out regardless of what WIFSIGNALED returns.
Low: fencing: Add stonith op return code string representation to log output.
Low: fencing: Remove xmlNode pointers from stonith callback function
Low: doc: Update todo list