ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-18 20:47:57 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #4647 from corda/4.0-release-notes-redux

Browse Source 
CORDA-2509 - Updating release notes
This commit is contained in:
Mike Hearn 2019-02-11 18:03:10 +01:00 committed by GitHub
commit e294bdd16b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 25 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/make-docsite.sh
View File

@ -18,4 +18,4 @@ echo "Generating HTML pages ..."
make html
echo "Moving PDF file from $(eval echo $PWD/build/latex/corda-developer-site.pdf) to $(eval echo $PWD/build/html/_static/corda-developer-site.pdf)"
mv $PWD/build/latex/corda-developer-site.pdf $PWD/build/html/_static/corda-developer-site.pdf
mv $PWD/build/latex/corda-developer-site.pdf $PWD/build/html/_static/corda-developer-site.pdf

27
docs/source/release-notes.rst
View File

@ -3,7 +3,7 @@ Release notes for Corda 4
.. _release_notes_v4_0:
Here we are, 9 months and 1500 plus commits later... and it's a bouncing baby software release!
Here we are, 10 months and 1500 plus commits later... and it's a bouncing baby software release!
We are really proud to release Corda 4 to the open source community today. It's been a long time in
the making, but we think you'll agree worth the wait.
@ -21,10 +21,31 @@ comes with those same guarantees. States and apps valid in Corda 3 are transpare
Additionally, be aware that the data model upgrades are changes to the Corda consensus rules. To use
apps that benefit from them, *all* nodes in a compatibility zone must be upgraded and the zone must be
enforcing that upgrade. This may take time in large zones like the testnet. Please take this into
enforcing that upgrade. This may take time in large zones like the TestNet. Please take this into
account for your own schedule planning.
.. contents::
Important note about Corda’s compatibility, upgrade and interoperability guarantees
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Corda platform places great emphasis on ensuring compatibility across versions and the ability to
upgrade/migrate data from previous versions to new versions. As a CorDapp developer or operator of a node,
it is important to understand these guarantees and how to take advantage of them. Please see :doc:`versioning` for
full information on Corda’s capabilities and platform commitments.
For Corda 4, these capabilities will be delivered progressively, across the 4.0 release, which is
available now, and the 4.1 release, which will follow in the coming weeks. Here is how the capability is split:
*Corda 4.0* delivers the full new suite of Platform version 4 features: Reference states, signature constraints,
and more. These features are summarised below. The API is stable and you can start developing new apps with it
today and upgrading existing apps to take advantage of the new features today. In addition, you can take these
apps live for new deployments.
*Corda 4.1* will deliver the ability to support mixed networks of Corda 3.3, Corda Enterprise 3.2 and Corda 4.1
nodes, and the ability to upgrade such nodes, even those with pre-existing data in their vaults, to Corda 4.1.
.. important:: To ensure we maintain our compatibility and data integrity commitments at all times, Corda 4.0 is configured to
refuse to start if it detects that its vault contains any version 3.x data; for such scenarios, please wait for Corda 4.1.
Changes for developers in Corda 4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~