[FAB-16303] GetHistoryForKey release note

In prior releases, the GetHistoryForKey chaincode API had no
guarantees on the order of returned results.
Starting in Fabric v2.0, the GetHistoryForKey chaincode API
will return results from newest to oldest in terms of ordered transaction
height (block height and transaction height within block).
This will allow applications to iterate through the top results
to understand recent changes to a key.

Change-Id: I747c35300819cf7427d601a1935766a8ce9aa840
Signed-off-by: David Enyeart <enyeart@us.ibm.com>

Author: denyeart

release_notes/v2.0.0.txt

@@ -54,7 +54,7 @@ installing chaincode by using different SDKs. To workaround the problem,
 package the chaincode prior to installation and instantiation, by using
 the "peer chaincode package" command.
 
-FAB-15366 Logger removed from chaincode shim
+FAB-15366 - Logger removed from chaincode shim
 Chaincode that used the shim's NewLogger() will need to shift to a new
 logging mechanism. Chaincode logging is intended to be the responsibility
 of the application developer. As such it should be handled using tools and
@@ -72,6 +72,15 @@ Chaincode implementations that used the entities extension package from an
 earlier version of Fabric will need to vendor a 1.x version of the package
 for as part of their chaincode package.
 
+FAB-16303 - GetHistoryForKey returns results from newest to oldest
+In prior releases, the GetHistoryForKey chaincode API had no
+guarantees on the order of returned results.
+Starting in Fabric v2.0, the GetHistoryForKey chaincode API
+will return results from newest to oldest in terms of ordered transaction
+height (block height and transaction height within block).
+This will allow applications to iterate through the top results
+to understand recent changes to a key.
+
 Known Vulnerabilities
 ---------------------
 FAB-8664 - Peer should detect and react when its org has been removed