Docs: minor change to the release notes.

Babies don't typically get delayed by a few months due to backwards compatibility fixes so the opening no longer made sense :)
This commit is contained in:
Mike Hearn 2019-02-20 21:08:18 +01:00
parent cac9b1cfc7
commit 01f0c4b3d2

View File

@ -3,19 +3,19 @@ Release notes for Corda 4
.. _release_notes_v4_0: .. _release_notes_v4_0:
Here we are, 11 months and 1500 plus commits later... and it's a bouncing baby software release! Welcome to the Corda 4 release notes. Please read these carefully to understand what's new in this
release and how the changes can help you. Just as prior releases have brought with them commitments
to wire and API stability, Corda 4 comes with those same guarantees. States and apps valid in
Corda 3 are transparently usable in Corda 4.
We are really proud to release Corda 4 to the open source community today. It's been a long time in For app developers, we strongly recommend reading ":doc:`app-upgrade-notes`". This covers the upgrade
the making, but we think you'll agree worth the wait. procedure, along with how you can adjust your app to opt-in to new features making your app more secure and
easier to upgrade in future.
Just as prior releases have brought with them commitments to wire and API stability, Corda 4 For node operators, we recommend reading ":doc:`node-upgrade-notes`". The upgrade procedure is simple but
comes with those same guarantees. States and apps valid in Corda 3 are transparently usable in Corda 4. it can't hurt to read the instructions anyway.
We strongly recommend reading ":doc:`app-upgrade-notes`". This covers the upgrade procedure, Additionally, be aware that the data model improvements are changes to the Corda consensus rules. To use
along with how you can adjust your app to opt-in to new features making your app more secure and
easier to upgrade.
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 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. account for your own schedule planning.