dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Typo of Deprecation as Depreciation on the release policy (#3467) 

A mistake I know so many people (including) myself have made and a super minor fix.

Signed-off-by: Lee Packham <me@leepackham.com>
This commit is contained in:
Lee Packham 2023-05-30 12:30:18 +01:00 committed by GitHub
parent 2b6c5804c5
commit a12c86c528
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/operations/support/support-release-policy.md
View File

@ -140,7 +140,7 @@ There is a process for applying breaking changes:
1. The breaking changes are applied two (2) releases after the release in which the deprecation was announced. 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. - 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
Deprecations appear in release notes under a section named “Deprecations”, which indicates: Deprecations appear in release notes under a section named “Deprecations”, which indicates: