Choose timezone
Your profile timezone:
SA2.3 meeting with QC, regarding metrics in Year 2
→
Europe/Zurich
CERN
CERN
Description
Meeting to discuss the key performance indicators and bug-tracking metrics to be shared between SA2.3 and SA1 QC.
Meeting Access Information:
- Meeting URL
http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MsMiMI2829DnDv989vDt9s
- Phone Bridge
ID: 357 6740
Central European Summer Time (+0200)
Start 2011-06-17 10:00
End 2011-06-17 11:00
Attendance: Eamonn, Claudio, Duarte, Alberto, Andres, Maria, Anders
Bug-tracker related Metrics
Open and closed priority bug needed in KSA1.x.
Action Point: Fixed Bugs plot, per category and a list of URLs pointing to each tracker item should be provided on a monthly basis by SA2.4.
Action Point: Eamonn should inform each middleware contact informing them that the UID needs to be changed to a URL (includes Laurence for Info. Sys. and Riccardo for StoRM).
EMT related metrics are not required by SA1, i.e Successful Builds metric or untouched bugs metric.
We will not cover any metrics related to testing for the remainder of the meeting, at Alberto's rightful request.
Bug density distribution will play a role in the KSA1.x KPIs.
The documentation metric can be obtained by hand using the tables of documentation produced by NA2.
The delay on release metric is one of particular interest to Maria. We will discuss it with Maria outside this meeting. SA1 at the moment produce it by hand for their reports.
5.4.2 and 5.4.4 relating to GGUS training and support tickets should indeed be aggregated to 5.4.1 as shown by KSA1.1.
Breakdown of KPIs
Looking at the KPIs themselves, the metrics group should not concern itself with the generate of KSA1.1 or KSA1.2, however we do present a table of the possible results that can be obtained in relation these statistics/metrics. This may prove useful to SA1.
Alberto suggests that SA1 open a ticket regarding the obtaining of KSA1.1 and 1.2 from the GGUS people. Contact them directly.
The metrics group should only concern itself with KSA1.3-1.5.
As can be seen from the bold highlighted text, there are a large number of possibilities for generating results for SA1. There can be number and trend, category or total, bug density or without bug density, defect or enhancement, high or immediate priority. In some cases there are 8 to 16 possible plots that can be produced.
Action Point: SA1 should fill out the table showing their top priority for plots required for KSA1.3-1.5 or values that they require if they don't require plots.
If the above action is not taken it is almost impossible for SA2.4 to produce plots that will be of much benefit to SA1.
Bug-tracker related Metrics
Open and closed priority bug needed in KSA1.x.
Action Point: Fixed Bugs plot, per category and a list of URLs pointing to each tracker item should be provided on a monthly basis by SA2.4.
Action Point: Eamonn should inform each middleware contact informing them that the UID needs to be changed to a URL (includes Laurence for Info. Sys. and Riccardo for StoRM).
EMT related metrics are not required by SA1, i.e Successful Builds metric or untouched bugs metric.
We will not cover any metrics related to testing for the remainder of the meeting, at Alberto's rightful request.
Bug density distribution will play a role in the KSA1.x KPIs.
The documentation metric can be obtained by hand using the tables of documentation produced by NA2.
The delay on release metric is one of particular interest to Maria. We will discuss it with Maria outside this meeting. SA1 at the moment produce it by hand for their reports.
5.4.2 and 5.4.4 relating to GGUS training and support tickets should indeed be aggregated to 5.4.1 as shown by KSA1.1.
Breakdown of KPIs
Looking at the KPIs themselves, the metrics group should not concern itself with the generate of KSA1.1 or KSA1.2, however we do present a table of the possible results that can be obtained in relation these statistics/metrics. This may prove useful to SA1.
Alberto suggests that SA1 open a ticket regarding the obtaining of KSA1.1 and 1.2 from the GGUS people. Contact them directly.
The metrics group should only concern itself with KSA1.3-1.5.
As can be seen from the bold highlighted text, there are a large number of possibilities for generating results for SA1. There can be number and trend, category or total, bug density or without bug density, defect or enhancement, high or immediate priority. In some cases there are 8 to 16 possible plots that can be produced.
Action Point: SA1 should fill out the table showing their top priority for plots required for KSA1.3-1.5 or values that they require if they don't require plots.
If the above action is not taken it is almost impossible for SA2.4 to produce plots that will be of much benefit to SA1.
There are minutes attached to this event.
Show them.
