This is an automated email from the ASF dual-hosted git repository.

yumeng pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 5267207feb docs: update deployment frequency definition (#562)
5267207feb is described below

commit 5267207feb0f4c4eb5b85d28a13880dd0db4e42b
Author: Louis.z <[email protected]>
AuthorDate: Sat Jun 17 21:01:30 2023 +0800

    docs: update deployment frequency definition (#562)
    
    Co-authored-by: Startrekzky <[email protected]>
---
 docs/Metrics/DeploymentFrequency.md                      | 16 ++++++++--------
 .../version-v0.17/Metrics/DeploymentFrequency.md         | 16 ++++++++--------
 2 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/docs/Metrics/DeploymentFrequency.md 
b/docs/Metrics/DeploymentFrequency.md
index 0e105f98fb..bae538ef0c 100644
--- a/docs/Metrics/DeploymentFrequency.md
+++ b/docs/Metrics/DeploymentFrequency.md
@@ -21,18 +21,18 @@ DORA dashboard. See [live 
demo](https://grafana-lake.demo.devlake.io/grafana/d/q
 
 ## How is it calculated?
 
-Deployment frequency is calculated based on the number of deployment days, not 
the number of deployments, e.g., daily, weekly, monthly, yearly.
+Deployment frequency is calculated based on the number of `deployment days`, 
not the number of deployments, e.g., daily, weekly, monthly, yearly.
 
 When there are multiple deployments triggered by one pipeline, tools like 
GitLab and BitBucket will generate more than one deployment. In these cases, 
DevLake will consider these deployments as ONE deployment and use the last 
deployment's finished date as the deployment finished date.
 
 Below are the benchmarks for different development teams from Google's report. 
DevLake uses the same benchmarks.
 
-| Groups            | Benchmarks                                     | DevLake 
Benchmarks                             |
-| ----------------- | ---------------------------------------------- | 
---------------------------------------------- |
-| Elite performers  | On-demand (multiple deploys per day)           | 
On-demand                                      |
-| High performers   | Between once per week and once per month       | Between 
once per week and once per month       |
-| Medium performers | Between once per month and once every 6 months | Between 
once per month and once every 6 months |
-| Low performers    | Fewer than once per six months                 | Fewer 
than once per six months                 |
+| Groups            | Benchmarks                                     | DevLake 
Benchmarks                             | The Criteria of DevLake Benchmarks     
           |
+| ----------------- | ---------------------------------------------- | 
---------------------------------------------- | 
--------------------------------------------------|
+| Elite performers  | On-demand (multiple deploys per day)           | 
On-demand                                      | Median Number of `Deployment 
Days` per Week >= 3  |
+| High performers   | Between once per week and once per month       | Between 
once per week and once per month       | Median Number of `Deployment Days` per 
Week >= 1  |
+| Medium performers | Between once per month and once every 6 months | Between 
once per month and once every 6 months | Median Number of `Deployment Days` per 
Month >= 1 |
+| Low performers    | Fewer than once per six months                 | Fewer 
than once per six months                 | Median Number of `Deployment Days` 
per Month < 1  |
 
 <p><i>Source: 2021 Accelerate State of DevOps, Google</i></p>
 
@@ -82,7 +82,7 @@ FROM
        WHERE $__timeFilter(cm.month_timestamp)
 ```
 
-If you want to measure in which category your team falls as in the picture 
shown below, run the following SQL in Grafana.
+If you want to measure in which category your team falls as in the picture 
shown below, run the following SQL in Grafana. Unlike monthly deployments which 
are based on the number of deployments, the metric below is based on 
`deployment days`.
 
 ![](/img/Metrics/deployment-frequency-text.jpeg)
 
diff --git a/versioned_docs/version-v0.17/Metrics/DeploymentFrequency.md 
b/versioned_docs/version-v0.17/Metrics/DeploymentFrequency.md
index e35e3e2750..469357aff3 100644
--- a/versioned_docs/version-v0.17/Metrics/DeploymentFrequency.md
+++ b/versioned_docs/version-v0.17/Metrics/DeploymentFrequency.md
@@ -19,18 +19,18 @@ DORA dashboard. See [live 
demo](https://grafana-lake.demo.devlake.io/grafana/d/q
 
 
 ## How is it calculated?
-Deployment frequency is calculated based on the number of deployment days, not 
the number of deployments, e.g., daily, weekly, monthly, yearly.
+Deployment frequency is calculated based on the number of `deployment days`, 
not the number of deployments, e.g., daily, weekly, monthly, yearly.
 
 When there are multiple deployments triggered by one pipeline, tools like 
GitLab and BitBucket will generate more than one deployment. In these cases, 
DevLake will consider these deployments as ONE deployment and use the last 
deployment's finished date as the deployment finished date.
 
 Below are the benchmarks for different development teams from Google's report. 
DevLake uses the same benchmarks.
 
-| Groups           | Benchmarks                                    | DevLake 
Benchmarks                             |
-| -----------------| --------------------------------------------- | 
---------------------------------------------- |
-| Elite performers | On-demand (multiple deploys per day)          | On-demand 
                                     |
-| High performers  | Between once per week and once per month      | Between 
once per week and once per month       |
-| Medium performers| Between once per month and once every 6 months| Between 
once per month and once every 6 months |
-| Low performers   | Fewer than once per six months                | Fewer 
than once per six months                 |
+| Groups            | Benchmarks                                     | DevLake 
Benchmarks                             | The Criteria of DevLake Benchmarks     
           |
+| ----------------- | ---------------------------------------------- | 
---------------------------------------------- | 
--------------------------------------------------|
+| Elite performers  | On-demand (multiple deploys per day)           | 
On-demand                                      | Median Number of `Deployment 
Days` per Week >= 3  |
+| High performers   | Between once per week and once per month       | Between 
once per week and once per month       | Median Number of `Deployment Days` per 
Week >= 1  |
+| Medium performers | Between once per month and once every 6 months | Between 
once per month and once every 6 months | Median Number of `Deployment Days` per 
Month >= 1 |
+| Low performers    | Fewer than once per six months                 | Fewer 
than once per six months                 | Median Number of `Deployment Days` 
per Month < 1  |
 
 <p><i>Source: 2021 Accelerate State of DevOps, Google</i></p>
 
@@ -91,7 +91,7 @@ FROM
 ORDER BY 1
 ```
 
-If you want to measure in which category your team falls as in the picture 
shown below, run the following SQL in Grafana.
+If you want to measure in which category your team falls as in the picture 
shown below, run the following SQL in Grafana. Unlike monthly deployments which 
are based on the number of deployments, the metric below is based on 
`deployment days`.
 
 ![](/img/Metrics/deployment-frequency-text.jpeg)
 

Reply via email to