Release notes

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Release notes are documents that are distributed with software products, sometimes when the product is still in the development or test state (e.g., a beta release). For products that have already been in use by clients, the release note is delivered to the customer when an update is released.[1][2]

Purpose and Responsibilities[edit]

Release notes are documents that are shared with end users, customers and clients of an organization. The definition of the terms 'End Users', 'Clients' and 'Customers' are very relative in nature and might have various interpretations based on the specific context. For instance, the Quality Assurance group within a software development organization can be interpreted as an internal customer. The release notes detail the corrections, changes or enhancements made to the service or product the company provides. This document is usually circulated only after the product or service is thoroughly tested and approved against the specification provided by the development team. However this document might also be provided as an artifact accompanying the deliverables for System Testing and System Integration Testing and other managed environments especially with reference to an information technology organization.[3]

Release notes can also contain test results and information about the test procedure. This kind of information gives readers of the release note more confidence in the fix/change done; this information also enables implementer of the change to conduct rudimentary acceptance tests.

Content and Format[edit]

There is no standard format for release notes that is followed throughout different organizations. Organizations normally adopt their own formatting styles based on the requirement and type of the information to be circulated. The content of release notes also vary according to the release type. For products that are at testing stage and that are newly released, the content is usually more descriptive compared to release notes for bug fixes and feature enhancements, which are usually brief. Release notes may include the following sections:

  • Header – Document Name (i.e. Release Notes), product name, release number, release date, note date, note version, etc.
  • Overview - A brief overview of the product and changes, in the absence of other formal documentation.
  • Purpose - A brief overview of the purpose of the release note with a listing of what is new in this release, including bug fixes and new features.
  • Issue Summary - A short description of the bug or the enhancement in the release.
  • Steps to Reproduce - The steps that were followed when the bug was encountered.
  • Resolution - A short description of the modification/enhancement that was made to fix the bug.
  • End-User Impact - What different actions are needed by the end-users of the application. This should include whether other functionality is impacted by these changes.
  • Support Impacts - Changes required in the daily process of administering the software.
  • Notes - Notes about software or hardware installation, upgrades and product documentation (including documentation updates)
  • Disclaimers - Company and standard product related messages. e.g.; freeware, anti-piracy, duplication etc.. See also Disclaimer.
  • Contact - Support contact information.

A release note is usually a terse summary of recent changes, enhancements and bug fixes in a particular software release. It is not a substitute for user guides. Release notes are frequently written in the present tense and provide information that is clear, correct, and complete.

See also[edit]


  1. ^ "JDK Release Notes". Retrieved 2019-02-18.
  2. ^ "Confluence Release Notes - Atlassian Documentation". Retrieved 2019-02-18.
  3. ^ comments, 07 Mar 2017 Ben CottonFeed 142up 6. "How to make release notes count". Retrieved 2019-02-18.

External links[edit]