From 17448ec84317c50d90d999a3ea169d929f628ae9 Mon Sep 17 00:00:00 2001 From: Ben Ashbaugh Date: Mon, 18 Sep 2023 18:40:23 -0700 Subject: [PATCH] clarify when to use tagged or released OpenCL API headers --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 2a2d8b9b..1a491896 100644 --- a/README.md +++ b/README.md @@ -110,9 +110,10 @@ break backward compatibility: * The OpenCL API headers for provisional features or provisional extensions may be changed in a way that breaks compatibility. -Applications are encouraged to use tagged or released OpenCL API headers to -avoid rare compatibility issues, if desired. The OpenCL API headers are tagged -at least as often as each OpenCL specification release. +Applications or libraries that require stable OpenCL API headers are encouraged +to use tagged or released OpenCL API headers. We will do our best to document +any breaking changes in the description of each release. The OpenCL API headers +are tagged at least as often as each OpenCL specification release. ## Directory Structure