Have Travis ensure that what's new is updated

Sometimes when PRs are merged I waste time going back to double check that what's new has been updated.

We should make a travis run for PRs only that fails if tests are modified and what's new isn't modified. Perhaps we should even check that the diff to what's new mentions the current PR# (although there are sometimes exceptions to this).

Does this seem a reasonable policy?