[SYCL][Doc] Add note on frozen ABI (#2686)

Co-authored-by: Alexander Batashev <[email protected]>

Author: romanovvlad

CONTRIBUTING.md

@@ -20,6 +20,11 @@ is strongly encouraged that you submit the patch to https://llvm.org/ directly.
 See [LLVM contribution guidelines](https://llvm.org/docs/Contributing.html)
 for more information.
 
+**Note (October, 2020)**: DPC++ runtime and compiler ABI is currently in frozen
+state. This means that no ABI-breaking changes will be accepted by default.
+Project maintainers may still approve breaking changes in some cases. Please,
+see [ABI Policy Guide](sycl/doc/ABIPolicyGuide.md) for more information.
+
 - Create a personal fork of the project on GitHub
   - For the DPC++ Compiler project, use **sycl** branch as baseline for your
     changes. See [Get Started Guide](sycl/doc/GetStartedGuide.md).

sycl/doc/ABIPolicyGuide.md

@@ -92,13 +92,22 @@ There is a set of tests to help identifying ABI changes:
   classes for layout changes, while `symbol_size` only checks `sizeof` for API
   classes. Changing the class layout is a breaking change.
 
-## Breaking ABI
+## Changing ABI
+
+**Note (October, 2020)**: DPC++ runtime and compiler ABI is currently in frozen
+state. This means that no ABI-breaking changes will be accepted by default.
+Project maintainers may still approve breaking changes in some cases. Please,
+try to avoid any breaking changes until freeze is lifted. If you need to change
+existing functionality, consider adding new APIs instead of replacing them.
+Also, please, avoid any changes, mentioned in the [Intro](#intro) section as
+breaking. Refer to the above guide to distinguish breaking and non-breaking
+changes. If not sure, do not hesitate to ask code owners for help.
 
 Whenever you need to change the existing ABI, please, follow these steps:
 
 1. Adjust you PR description to reflect (non-)breaking ABI changes. Make sure
    it is clear, why breaking ABI is necessary.
 2. Fix failing ABI tests in your Pull Request. Use aforementioned techniques to
    update test files.
-3. If Pull Request introduces a breaking change, update the library version
-   according to the policies.
+3. ~~If Pull Request introduces a breaking change, update the library version~~
+   ~~according to the policies.~~ **(See note above)**