Post History
In my opinion Release Notes should be written in a technical style, focused on the technical implications of the most recent changes. This makes them sort of a mix between the two worlds - you want...
Answer
#4: Attribution notice removed
by
System
·
2019-12-12T23:01:20Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/33229 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
by
System
·
2019-12-08T07:56:12Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/33229 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
In my opinion Release Notes should be written in a technical style, focused on the technical implications of the most recent changes. This makes them sort of a mix between the two worlds - you want to target decision makers and technical people and tell them what has changed when compared to the older version of the software, emphasizing what the problems are that may arise from these changes or what the problems are that these changes fix. You don't want to sell the newest features and the whole product to the decision makers - they have already bought the product and want to know whether changing to the new version will cost them too much or if the fixes will offset the update costs. You also don't want to sell the product to the technical people - they want to know what of their daily work will change by using the new version. But you want to make it easy and fast to understand for everyone familiar with the old version of the software.
#1: Imported from external source
by
System
·
2018-02-13T18:41:00Z (over 6 years ago)
Original score: 2