Merge pull request #2685 from hhunter-ms/support_grammar_fix

support release fix

daprdocs/content/en/operations/support/support-release-policy.md

@@ -8,7 +8,7 @@ description: "Runtime and SDK release support and upgrade policies "
 
 ## Introduction
 
-This topic details the supported versions of Dapr releases, the upgrade policies, and how deprecations and breaking changes are communicated.
+This topic details the supported versions of Dapr releases, the upgrade policies and how deprecations and breaking changes are communicated in all Dapr repositories (runtime, CLI, SDKs, etc) at versions 1.x and above.
 
 Dapr releases use `MAJOR.MINOR.PATCH` versioning. For example, 1.0.0.
 
@@ -16,7 +16,7 @@ Dapr releases use `MAJOR.MINOR.PATCH` versioning. For example, 1.0.0.
 | ---------- | ----------- |
 | `MAJOR`    | Updated when there’s a non-backward compatible change to the runtime, such as an API change. A `MAJOR` release can also occur then there is a considered a significant addition/change of functionality that needs to differentiate from the previous version. |
 | `MINOR`    | Updated as part of the regular release cadence, including new features, bug, and security fixes. |
-| `PATCH`    | Incremented for bug and security hot fixes. |
+| `PATCH`    | Incremented for a critical issue (P0) and security hot fixes. |
 
 A supported release means:
 
@@ -30,6 +30,7 @@ There will be at least 6 weeks between major.minor version releases giving users
 Patch support is for supported versions (current and previous).
 
 ## Supported versions
+
 The table below shows the versions of Dapr releases that have been tested together and form a "packaged" release. Any other combinations of releases are not supported.
 
 | Release date | Runtime     | CLI  | SDKs  | Dashboard  | Status |
@@ -57,11 +58,12 @@ The table below shows the versions of Dapr releases that have been tested togeth
 | Jul 26th 2021 | 1.3</br>   | 1.3.0 | Java 1.2.0 </br>Go 1.2.0 </br>PHP 1.1.0 </br>Python 1.2.0 </br>.NET 1.3.0 | 0.7.0 | Unsupported         |
 
 ## Upgrade paths
+
 After the 1.0 release of the runtime there may be situations where it is necessary to explicitly upgrade through an additional release to reach the desired target. For example, an upgrade from v1.0 to v1.2 may need to pass through v1.1.
 
 The table below shows the tested upgrade paths for the Dapr runtime. Any other combinations of upgrades have not been tested.
 
-General guidance on upgrading can be found for [self hosted mode]({{<ref self-hosted-upgrade>}}) and [Kubernetes]({{<ref kubernetes-upgrade>}}) deployments. It is best to review the target version release notes for specific guidance.
+General guidance on upgrading can be found for [self hosted mode]({{< ref self-hosted-upgrade >}}) and [Kubernetes]({{< ref kubernetes-upgrade >}}) deployments. It is best to review the target version release notes for specific guidance.
 
 |  Current Runtime version | Must upgrade through  | Target Runtime version   |
 |--------------------------|-----------------------|------------------------- |
@@ -79,26 +81,63 @@ General guidance on upgrading can be found for [self hosted mode]({{<ref self-ho
 | 1.8.0                    |                   N/A |                    1.8.2 |
 
 
-## Feature and deprecations
+## Breaking changes and deprecations
-There is a process for announcing feature deprecations.  Deprecations are applied two (2) releases after the release in which they were announced. For example Feature X is announced to be deprecated in the 1.0.0 release notes and will then be removed in 1.2.0.
+
+### Breaking changes 
+
+Breaking changes are defined as a change to any of the following that cause compilation errors or undesirable runtime behavior to an existing 3rd party consumer application or script after upgrading to the next stable minor version of a Dapr artifact (SDK, CLI, runtime, etc):
+
+- Code behavior
+- Schema
+- Default configuration value
+- Command line argument
+- Published metric
+- Kubernetes CRD template
+- Publicly accessible API
+- Publicly visible SDK interface, method, class, or attribute
+
+Breaking changes can be applied right away to the following cases:
+
+- Projects versioned at 0.x.y
+- Preview feature
+- Alpha API
+- Preview or Alpha interface, class, method or attribute in SDK
+- Dapr Component in Alpha or Beta
+- Components-Contrib interface
+- URLs in Docs and Blog
+- An **exceptional** case where it is **required** to fix a critical bug or security vulnerability.
+
+#### Process for applying breaking changes
+
+There is a process for applying breaking changes:
+
+1. A deprecation notice must be posted as part of a release. 
+1. The breaking changes are applied two (2) releases after the release in which the deprecation was announced. 
+   - For example, feature X is announced to be deprecated in the 1.0.0 release notes and will then be removed in 1.2.0.
+
+### Depreciations
 
 Deprecations appear in release notes under a section named “Deprecations”, which indicates:
+
 - The point in the future the now-deprecated feature will no longer be supported. For example release x.y.z.  This is at least two (2) releases prior.
 - Document any steps the user must take to modify their code, operations, etc if applicable in the release notes.
 
 After announcing a future breaking change, the change will happen in 2 releases or 6 months, whichever is greater. Deprecated features should respond with warning but do nothing otherwise.
 
 ### Announced deprecations
+
 | Feature               |   Deprecation announcement   | Removal       |
 |-----------------------|-----------------------|------------------------- |
 | GET /v1.0/shutdown API (Users should use [POST API]({{< ref kubernetes-job.md >}}) instead)             |                 1.2.0 |                    1.4.0 |
 | Java domain builder classes deprecated (Users should use [setters](https://github.com/dapr/java-sdk/issues/587) instead) | Java SDK 1.3.0 | Java SDK 1.5.0 |
-| Service invocation will no longer provide a default content type header of `application/json` when no content-type is specified. You must explictly [set a content-type header]({{<ref "service_invocation_api.md#request-contents" >}}) for service invocation if your invoked apps rely on this header. |                 1.7.0 |                    1.9.0 |
+| Service invocation will no longer provide a default content type header of `application/json` when no content-type is specified. You must explictly [set a content-type header]({{< ref "service_invocation_api.md#request-contents" >}}) for service invocation if your invoked apps rely on this header. |                 1.7.0 |                    1.9.0 |
 
 ## Upgrade on Hosting platforms
+
 Dapr can support multiple hosting platforms for production. With the 1.0 release the two supported platforms are Kubernetes and physical machines. For Kubernetes upgrades see [Production guidelines on Kubernetes]({{< ref kubernetes-production.md >}})
 
 ### Supported versions of dependencies 
+
 Below is a list of software that the latest version of Dapr (v{{% dapr-latest-version long="true" %}}) has been tested against. 
 
 | Dependency            |   Supported Version                                                                                                              |
@@ -108,4 +147,5 @@ Below is a list of software that the latest version of Dapr (v{{% dapr-latest-ve
 | [Prometheus](https://prometheus.io/download/)             |                                                                                                                              v2.28 |
 
 ## Related links
-* Read the [Versioning policy]({{< ref support-versioning.md >}})
+
+- Read the [Versioning policy]({{< ref support-versioning.md >}})