mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2025-06-14 18:53:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: correct typos in struct field comments and release.md

Browse Source 
corrected strings in the release guide and util server.

Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit is contained in:
Humble Chirammal
2022-04-07 17:04:25 +05:30
committed by mergify[bot]
parent 4100ad2406
commit 959df4dbac
4 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/development-guide.md
View File

@ -25,7 +25,7 @@ it is **highly** encouraged to:
package](https://github.com/ceph/go-ceph). It is required to install the
Ceph C headers in order to compile Ceph-CSI. The packages are called
`librados-devel` and `librbd-devel` on many Linux distributions. See the
[go-ceph installaton
[go-ceph installation
instructions](https://github.com/ceph/go-ceph#installation) for more
details.
* Run
@ -169,7 +169,7 @@ The `component` in the subject of the commit message can be one of the following
* `doc`: documentation updates
* `util`: utilities shared between components use `cephfs` or `rbd` if the
change is only relevant for one of the type of storage
* `journal`: any of the journalling functionalities
* `journal`: any of the journaling functionalities
* `helm`: deployment changes for the Helm charts
* `deploy`: updates to Kubernetes templates for deploying components
* `build`: anything related to building Ceph-CSI, the executable or container
@ -312,12 +312,12 @@ Right now, we also have below commands to manually retrigger the CI jobs
**Caution**: Please do not retrigger the CI jobs without an understanding of
the root cause, because:
* We may miss some of the important corner cases which are true negatives,
* We may miss some important corner cases which are true negatives,
and hard to reproduce
* Retriggering jobs for known failures can unnecessarily put CI resources
under pressure
Hence it is recommended that you please go through the CI logs first, if you
Hence, it is recommended that you please go through the CI logs first, if you
are certain about the flaky test failure behavior, then comment on the PR
indicating the logs about a particular test that went flaky and use the
appropriate command to retrigger the job[s].