Add M9 draft change log

docs/source/changelog.rst

@@ -1,11 +1,17 @@
-Release notes
-=============
+Changelog
+=========
 
 Here are brief summaries of what's changed between each snapshot release.
 
 Milestone 9
 -----------
 
+* With thanks to `Thomas Schroeter <https://github.com/thschroeter>`_ for the Byzantine fault tolerant (BFT)
+  notary prototype.
+* Web server is a separate JAR.  This is a breaking change. The new webserver JAR (``corda-webserver.jar``)
+  must be invoked separately to node startup, using the command``java -jar corda-webserver.jar`` in the same
+  directory as the ``node.conf``. Further changes are anticipated in upcoming milestone releases.
+
 * API:
 
     * Pseudonymous ``AnonymousParty`` class added as a superclass of ``Party``.
@@ -14,12 +20,35 @@ Milestone 9
       captured in an object that can be passed around.
     * ``CordaPluginRegistry`` method ``registerRPCKryoTypes`` is renamed ``customizeSerialization`` and the argument
       types now hide the presence of Kryo.
+    * New extension functions for encoding/decoding to base58, base64, etc. See
+      ``core/src/main/kotlin/net/corda/core/crypto/EncodingUtils.kt``
+    * Add ``openAttachment`` function to Corda RPC operations, for downloading an attachment from a node's data storage.
+    * Add ``getCashBalances`` function to Corda RPC operations, for getting cash balances from a node's vault.
+
+* Configuration:
+    * ``extraAdvertisedServiceIds`` config is now a list of strings, rather than a comma separated string. For example
+      ``[ "corda.interest_rates" ]`` instead of ``"corda.interest_rates"``.
+
+* Flows:
+    * Split ``CashFlow`` into separate ``CashIssueFlow``, ``CashPaymentFlow`` and ``CashExitFlow`` so that permissions can
+      be assigned individually.
+    * Split single example user into separate "bankUser" and "bigCorpUser" so that permissions for the users make sense
+      rather than being a combination of both roles.
+    * ``ProgressTracker`` emits exception thrown by the flow, allowing the ANSI renderer to correctly stop and print the error
 
 * Object Serialization:
 
     * Consolidated Kryo implementations across RPC and P2P messaging with whitelisting of classes via plugins or with
       ``@CordaSerializable`` for added node security.
 
+* Privacy:
+    * Non-validating notary service now takes in a ``FilteredTransaction`` so that no potentially sensitive transaction
+      details are unnecessarily revealed to the notary
+
+* General:
+    * Add vault service persistence using Requery
+    * Certificate signing utility output is now more verbose
+
 Milestone 8
 -----------
 

docs/source/index.rst

@@ -125,7 +125,7 @@ Documentation Contents:
    setting-up-a-corda-network
    secure-coding-guidelines
    release-process
-   release-notes
+   changelog
    codestyle
    building-the-docs
    further-notes-on-kotlin

docs/source/release-process.rst

@@ -27,7 +27,7 @@ Steps to cut a release
 
 1. Pick a commit that is stable and do basic QA: run all the tests, run the demos.
 2. Review the commits between this release and the last looking for new features, API changes, etc. Make sure the
-   summary in the current section of the :doc:`release-notes` is correct and update if not. Then move it into the right
+   summary in the current section of the :doc:`changelog` is correct and update if not. Then move it into the right
    section for this release. This is the right place to put any advice on how to port app code from the last release.
 3. Additionally, if there are any new features or APIs that deserve a new section in the docsite and the author didn't
    create one, bug them to do so a day or two before the release.