Also some times worth highlighting things the end user may want to change in their configurations or workflow.

EDIT: I like @Henrik's comment

Most end users don't care about the test result. They expect it to have high quality no matter what the release note says.

EDIT: Also like @ddyer's answer

The most important thing about release notes is to be aware that every
additional sentence loses another 10% of the readers. So you must
strictly prioritize what your current users need to know about the
release.

The most important thing about release notes is to be aware that every additional sentence loses another 10% of the readers. So you must strictly prioritize what your current users need to know about the release.

each line might lose 10% of casual, uninterested (or lazy) readers. Those readers are the ones your release notes are not written for. The ones who care about what you've done will read them all and thank you for each relevant line - you only have to be careful about including fluff that really needs to go into the documentation proper.
– gbjbaanbOct 5 '12 at 17:21