DevYoungHulk opened a new issue, #7873:
URL: https://github.com/apache/incubator-devlake/issues/7873
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
## Question
I had some questions about this calculation logic when using devlake for
DORA metrics calculations.
https://devlake.apache.org/docs/Metrics/LeadTimeForChanges
This document describes the calculation of 'Median Lead Time for Changes'
using PR cycle time. However, the example only mentions the case where one PR
corresponds to one deployment.
My question is if we have multiple PRs in one deployment, should all of them
be calculated in Lead Time for Changes.
For example i have multiple PRs in one deployment: PR1 (commit1,commit2),
PR2 (commit3,commit4), PR3 (commit5)
'Lead Time for Change' should calculate the time cover all **commit1....
...commit5** or **Median(PR1,PR2,PR3 to deploy)**
Translated with DeepL.com (free version)
## Screenshots
If applicable, add screenshots to help explain.
## Additional context
Add any other context here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
