Skip to content
Snippets Groups Projects
Commit d132d07c authored by Mark Wood's avatar Mark Wood
Browse files

Merge branch 'add-deprecation-epic-gitaly-direction' into 'master'

Add deprecation and removal section to Gitaly Direction

Closes #13051

See merge request !98809
parents a6e22dbe 99145770
No related branches found
No related tags found
1 merge request!98809Add deprecation and removal section to Gitaly Direction
Pipeline #469099684 passed
......@@ -278,6 +278,14 @@ Customers may not desire to utilize Gitaly Cluster for the following reasons:
 
As we [mentioned above](https://about.gitlab.com/direction/create/gitaly/#improved-documentation-for-gitaly-and-gitaly-cluster), one of our priorities is to improve the Gitaly Cluster documentation. In order to do this, we would appreciate any problems be raised as an issue under our [documentation epic](https://gitlab.com/groups/gitlab-org/-/epics/5075). Additionally, if you receive assistance from the Gitaly team in resolving a customer issue, please help us clarify our documentation to help future teammates and customers.
 
## Deprecations and Changes
As Gitaly and Gitaly Cluster evolve, it is sometimes necessary to deprecate features. When this occurs, we will follow the documented [Deprecations, removals and breaking changes](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes) procedure. This ensures that all stable counterparts within GitLab are informed, and that the [GitLab Documentation](https://docs.gitlab.com/ee/update/deprecations) is also updated to keep our customers informed.
In addition, we will track all deprecations throughout the 14.x milestones, and breaking changes occurring in the 15.0 milestone on the following epic:
- [Gitaly 14.x through 15.0 Deprecations and Removals](https://gitlab.com/groups/gitlab-org/-/epics/7552)
## Top Customer Success/Sales issue(s)
 
<!--
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment