notify formatter of different failure types
track failed notifications rather than examples

note I'm in half a mind to track these in the reporter instead, WDYT
@myron_marston?
extract failure message lines
Updated travis build scripts (from rspec-dev)
Merge pull request #1517 from rspec/update-travis-build-scripts-2014-05-05-for-master

Updates from rspec-dev (2014-05-05)
Clarify changelog entry.

`expect_with :stdlib` is not supported in RSpec 3;
it's `expect_with :minutest` or `expect_with :test_unit` now.

[ci skip]
Reword sentence for greater clarity.

I originally took "it will fail to communicate" to mean
that it won't communicate rather than meaning the example
will be marked as failed in order to communicate.

[ci skip]
Use `RSpec.describe`.

This is the "primary" entry point in rspec 3 rather
than the monkey-patched `main.describe`

[ci skip]
extract backtrace handling
move specs for reading backtrace lines, this will need more refactoring me thinks
update yard
minitest assertion output changed, unsure why
use instance_doubles
changelog for #1510
Merge pull request #1518 from rspec/doc-improvements-2014-05-06

Doc improvements
Merge pull request #1510 from rspec/extract_formatter_backtrace_handling

Extract formatter backtrace handling
track example state in the reporter
Extract profiling to notifications + formatter
use formatter loader to configure profiler
use formatter helper to run notification (makes it less deterministic on time)