message: Update release policy for LTS
diff: @@ -69,8 +69,9 @@ Operations compatibility
  Support policy
  --------------
  -In addition to the latest release, CCF will provide security patches and bugfixes on two long term support releases at any given time. These releases are guaranteed to be API-stable, but not ABI-stable.
  -Applications will need to rebuild to pick up updates, but will not need to change their code.
  +In addition to the latest release, CCF aims to provide security patches and bugfixes on two long term support releases at any given time. These releases are guaranteed to be API-stable, but not ABI-stable. Applications will need to rebuild to pick up updates, but will not need to change their code.
  +
  +From 2.0.0 onwards, LTS patches will be released no more frequently than monthly, with an exception for critical fixes. LTS patches will pick up third-party dependency patches systematically, as long as they have been out for more than 14 days at the time of the release, again with an exception for critical fixes.
  A long term support release (LTS) will be supported for 1 year starting from its release date. That means that when a new LTS comes out, users effectively have a 6 months window to upgrade to the latest LTS.
  @@ -78,3 +79,10 @@ REST API guarantees spelled out in the first section apply across releases, but
  .. image:: /img/ccf_release.png
  :alt: Release
  +
  +CCF 1.0 Sunset
  +-----------------
  +
  +[CCF 1.0](https://github.com/microsoft/CCF/releases/tag/ccf-1.0.0) was released on April 30, 2021, and will go out of support after the June 2022 release of Open Enclave, which will remove support for mbedTLS 2.16 that CCF 1.0 depends on. Porting CCF 1.0 to mbedTLS 2.28 would not make sense now that CCF 2.0 has migrated completely to OpenSSL.
  +
  +Users are encouraged to try the latest [CCF 2.0 release candidate](https://github.com/microsoft/CCF/releases/tag/ccf-2.0.0-rc4), and to consider migrating.
  