Release notes

This split is for clarity and differentiation of feature-highlights from bugs, change requests (CRs) or improvements on the other side.

For instance, the Quality Assurance group within a software development organization can be interpreted as an internal customer.

[6] Release notes detail the corrections, changes or enhancements (functional or non-functional) made to the service or product the company provides.

[10] Release notes can also be interpreted as describing how to install or build the software, instead of highlighting new features or resolved bugs.

Release notes are frequently written in the present tense and provide information that is clear, correct, and complete.