The purpose of the release management practice is to make new and changed services and features available for use.
Release: A version of a service or other configuration item, or a collection of configuration items, that is made available for use.
https://wiki.process-symphony.com.au/framework/lifecycle/process/release-management-itil-4/

A known error is a problem that has been analysed but not resolved1. This means that the root cause of the problem has been identified, but a permanent solution has not been implemented yet2. A known error can be recorded in a known error database (KEDB) and linked to related incidents and problems3. References: ITIL Foundation - ITIL 4 Edition, page 15; ITIL 4 - A Pocket Guide, page 35; ITIL 4 Practice Guide: Problem Management, page 8.

It is important to understand the difference in these terms not just for clarity, but because outputs are much easier to measure than outcomes.
* Outputs are nearly always quantitative, with data available to show whether these have been delivered.
Outputs are easy to report on and to validate. There is no grey area.
* Outcomes are more challenging to verify because they are both qualitative and quantitative. Whether your outcomes have been achieved will rely, to a great extent, on the perception of the people who receive the service. Perceptions are not easy to measure or report on, but it is essential you find a way to do so.
https://www.bmc.com/blogs/outcomes-vs-outputs/