Talk:Release notes

Bugs
--Phaedreus 18:36, 19 September 2007 (UTC) Hi, Can anyone please enlighten me as what exactly is intended to be there in section 3 - bug fixes. Are these open bugs/issues from the last release OR all the bug fixes of internal development cycle of current release are reported here as well?

It seems to suggest that a release note is only concerned with one particular issue/bug resolution, this is not what I use release notes for, they are to release a baselined piece of software, which may only resolve one issue, but generally address many issues in one release —Preceding unsigned comment added by 217.33.105.192 (talk) 16:20, 6 January 2010 (UTC)

Best Practice
Understood there is no standard, IEC, IEEE, ISO for release notes, BUT should there be one? I say yes. Has there been any approach to this topic before? Pros and Cons? Surely not the right platform (Wikipedia) to discuss, but clearly you cannot compare or discuss Release notes of Games, Apps, etc. with release notes of NASA-Mil-Automotive embedded devices. Anyone on this topic? Searching https://stackoverflow.com/search?q=release+notes also giving a poor picture on the topic. Also correlates with Release Management I think.--LS (talk) 10:23, 15 December 2020 (UTC)

Approval
Hi, this sentence without reference "The document is usually circulated only after the product or service is tested and approved against the specification provided by the development team." is not the case. Release notes are not formal requirements documents. In base case, they can be linked to requirements, but very rarely this is intended because requirements/specifications is an in-house topic (expertise, sometimes even secret). Software is, especially in agile fashion, release on regular basis "mvp" and needs until the end to reach point of "approval against specification". Removing this part therefore. ✅ --17387349L8764 (talk) 16:44, 25 March 2021 (UTC)