Documentation Metrics


All metrics used in the quality model are described thereafter, with useful information and references. They are classified according to their source. Please note also that several other metrics may be retrieved but not used in the quality model.



  • Number of downloads on the web site ( DL_REPO_1M )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    The number of downloads on the web site of the project (download page) during last three months. Example of download page (for CDT) : http://www.eclipse.org/downloads/ .

  • Number of downloads on update site ( DL_UPDATE_SITE_1M )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    The number of downloads on the update site of the project during last three months. Is computed using successful and failed installs from marketplace.

  • IP log code coverage ( IP_LOG_COV )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Percentage of contributions covered by an appropriate IP log.

    Eclipse foundation has a very strict IP policy and this measure should always be 100%.

  • ITS issues changed lifetime ( ITS_CHANGED )

    Provided by: EclipseIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of updates on issues during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Update means an operation on a ticket changing its state, or adding information. Opening and closing a ticket are considered as updates. Identities of updaters are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • ITS issues changers lifetime ( ITS_CHANGERS )

    Provided by: EclipseIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of distinct identities updating tickets during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Update means an operation on a ticket changing its state, or adding information. Opening and closing a ticket are considered as updates. Identities of updaters are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • ITS issues closed lifetime ( ITS_CLOSED )

    Provided by: EclipseIts

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Number of issues closed during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Opened means that the ticket information was submitted to the issue traking system for the first time for that ticket. Identities of openers are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included). Number of lines are those calculated at the end of the period of analysis.

  • ITS issues closed 1 month ( ITS_CLOSED_30 )

    Provided by: EclipseIts

    Used by: QM_ITS

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Number of issues closed during the last month in the issue tracking system.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Opened means that the ticket information was submitted to the issue traking system for the first time for that ticket. Identities of openers are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included). Number of lines are those calculated at the end of the period of analysis.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ITS issue closers lifetime ( ITS_CLOSERS )

    Provided by: EclipseIts

    Used by:

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of distinct identities closing tickets during during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Update means an operation on a ticket changing its state, or adding information. Opening and closing a ticket are considered as updates. Identities of updaters are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • ITS issue closers 1 month ( ITS_CLOSERS_30 )

    Provided by: EclipseIts

    Used by: QM_ITS

    Scale: 1 < 2 ≤ 2 < 4 ≤ 3 < 9.75 ≤ 4 < 80 ≤ 5

    Number of distinct identities closing tickets during the last month in the issue tracking system.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Update means an operation on a ticket changing its state, or adding information. Opening and closing a ticket are considered as updates. Identities of updaters are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ITS issues opened lifetime ( ITS_OPENED )

    Provided by: EclipseIts

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Number of issues opened during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Opened means that the ticket information was submitted to the issue traking system for the first time for that ticket. Identities of openers are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included). Number of lines are those calculated at the end of the period of analysis.

  • ITS issue openers lifetime ( ITS_OPENERS )

    Provided by: EclipseIts

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Number of distinct identities opening tickets during the overall time range covered by the analysis.

    The subset of tickets considered from the issue tracking system are those specified in the project documentation, for example by specifying a tracker or a project name appearing in ticket data. Opened means that the ticket information was submitted to the issue traking system for the first time for that ticket. Identities of openers are the character strings found in the corresponding field in the ticket information. Time range is measured as a calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included). Number of lines are those calculated at the end of the period of analysis.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Number of jobs ( JOBS )

    Provided by: Hudson

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    The total number of jobs defined on the Hudson engine.

  • Number of failed jobs ( JOBS_FAILED_1W )

    Provided by: Hudson

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    The number of jobs that failed during last week on the Hudson engine.

  • Number of green jobs ( JOBS_GREEN )

    Provided by: Hudson

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    The number of green(successful) jobs on the Hudson engine.

    Green (or blue) jobs in Hudson define successful builds.

  • Number of red jobs ( JOBS_RED )

    Provided by: Hudson

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    The number of red (failed) jobs on the Hudson engine.

    Red jobs in Hudson define failed builds.

  • Number of yellow jobs ( JOBS_YELLOW )

    Provided by: Hudson

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    The number of yellow (unstable) jobs on the Hudson engine.

    Yellow jobs in Hudson define unstable builds. According to Hudson's documentation, a build is unstable if it was built successfully and one or more publishers report it unstable. For example if the JUnit publisher is configured and a test fails then the build will be marked unstable.

  • License identification ( LIC_IDENT )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Is there a list of the different licences used in the product?

    This measure may use an external tool like Ninka (ninka.turingmachine.org) to identify the licence of components used in the project. Another way would be to identify a file named LICENCES in the root folder.

  • Number of favourites on the Marketplace ( MKT_FAV )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 10 ≤ 2 < 30 ≤ 3 < 70 ≤ 4 < 300 ≤ 5

    The number of favourites on the Eclipse Marketplace for the project.

    This measure uses the MarketPlace REST API to retrieve the number of registered users who marked this project as a favourite. If the project is not registered on the Marketplace, the metric should be zero.

  • Number of successfull installs on the Marketplace ( MKT_INSTALL_SUCCESS_1M )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 100 ≤ 2 < 500 ≤ 3 < 1000 ≤ 4 < 10000 ≤ 5

    The number of successful installs for the project as reported on the Marketplace during the last three months.

    This measure uses the list of successful installs available on the Marketplace for every registered project. Here is an example of log page, metrics tab. If the project is not registered on the Marketplace, the metric should be zero.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ML authors ( MLS_SENDERS_30 )

    Provided by: EclipseMls

    Used by: QM_DIVERSITY

    Scale: 1 < 1.5 ≤ 2 < 3 ≤ 3 < 7.5 ≤ 4 < 26 ≤ 5

    Number of distinct senders for messages dated during the last month, in developer mailing list archives.

    Developer mailing list is the list or lists considered as 'for developers' in the project documentation. The date used is the mailing list server date, as stamped in the message. Time range is measured as three calendar months period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included). Distinct senders are those with distinct email addresses. Email addresses used are the strings found in 'From:' fields in messages.

    Note that developer communications are measured through the mailing list, and user communications are measured through the forums.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ML posts ( MLS_SENT_30 )

    Provided by: EclipseMls

    Used by: QM_ACTIVITY

    Scale: 1 < 2 ≤ 2 < 6 ≤ 3 < 22 ≤ 4 < 103 ≤ 5

    Number of messages dated during the last month, in developer mailing list archives.

    Developer mailing list is the list or lists considered as 'for developers' in the project documentation. The date used is the mailing list server date, as stamped in the message. Time range is measured as one calendar month period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

    Note that developer communications are measured through the mailing list, and user communications are measured through the forums.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ML sent responses ( MLS_SENT_RESPONSE )

    Provided by: EclipseMls

    Used by: QM_SUPPORT

    Scale: 1 < 2 ≤ 2 < 6 ≤ 3 < 22 ≤ 4 < 103 ≤ 5

    Number of responses (i.e. replies in a thread) in developer mailing list archives.

    Threads are identified using 'In-Reply-To' message headers. Developer mailing list is the list or lists considered as 'for developers' in the project documentation.

    Note that developer communications are measured through the mailing list, and user communications are measured through the forums.

  • ML threads ( MLS_THREADS )

    Provided by: EclipseMls

    Used by: QM_SUPPORT

    Scale: 1 < 2 ≤ 2 < 6 ≤ 3 < 22 ≤ 4 < 103 ≤ 5

    Number of threads (i.e. an email and its replies) in developer mailing list archives.

    Threads are identified using 'In-Reply-To' message headers. Developer mailing list is the list or lists considered as 'for developers' in the project documentation.

    Note that developer communications are measured through the mailing list, and user communications are measured through the forums.

  • Number of milestones ( PLAN_MILESTONES_VOL )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 1 ≤ 2 < 5 ≤ 3 < 10 ≤ 4 < 20 ≤ 5

    The number of milestones that occured during the last five releases.

    Milestones are retrieved from the PMI file and are counted whatever their target release is. Milestones are useful to assess the maturity of the release and improves predictability of the project's output, in terms of quality and time.

  • Project is on time for next milestone ( PLAN_NEXT_MILESTONE )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Is the project on time for the next milestone?

  • Reviews success rate ( PLAN_REVIEWS_SUCCESS_RATE )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 20 ≤ 2 < 40 ≤ 3 < 60 ≤ 4 < 80 ≤ 5

    What is the percentage of successful reviews over the past 5 releases?

    The reviews are retrieved from the project management infrastructure record, and are considered successful if the entry is equal to success. If there are less than 5 releases defined, the percentage is computed on these only.

  • ITS information ( PMI_ITS_INFO )

    Provided by: EclipsePmi

    Used by: QM_ITS

    Scale: 1 < 2 ≤ 2 < 3 ≤ 3 < 4 ≤ 4 < 5 ≤ 5

    Is the bugzilla info correctly filled in the PMI records?

    The project management infrastructure file holds information about one or more bugzilla instances. This test checks that at least one bugzilla instance is defined, with a product identifier, a create_url to enter a new issue, and a query_url to fetch all the issues for the project.

  • SCM information ( PMI_SCM_INFO )

    Provided by: EclipsePmi

    Used by: QM_SCM

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 4 ≤ 5

    Is the source_repo info correctly filled in the PMI records?

    The project management infrastructure file holds information about one or more source repositories. This test checks that at least one source repository is defined, and accessible.

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • SCM committers ( SCM_AUTHORS_30 )

    Provided by: EclipseScm

    Used by: QM_DIVERSITY , QM_SCM

    Scale: 1 < 1 ≤ 2 < 2 ≤ 3 < 3 ≤ 4 < 18 ≤ 5

    Total number of identities found as authors of commits in source code management repositories dated during the last three months.

    Source code management repositories are those considered as such in the project documentation. Commits in all branches are considered. Date used for each commit is 'author date' (when there is a difference between author date and committer date). An identity is considered as author if it appears as such in the commit record (for systems logging several identities related to the commit, authoring identity will be considered). Time range is measured as three calendar months period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • SCM Commits ( SCM_COMMITS_30 )

    Provided by: EclipseScm

    Used by: QM_ACTIVITY , QM_SCM

    Scale: 1 < 2 ≤ 2 < 5 ≤ 3 < 13 ≤ 4 < 121 ≤ 5

    Total number of commits in source code management repositories dated during the last three months.

    Source code management repositories are those considered as such in the project documentation. Commits in all branches are considered. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as three calendar months period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • Files committed ( SCM_FILES )

    Provided by: EclipseScm

    Used by: QM_ACTIVITY

    Scale: 1 < 3 ≤ 2 < 19 ≤ 3 < 95.75 ≤ 4 < 2189 ≤ 5

    Total number of files touched by commits in source code management repositories dated during the last three months.

    Source code management repositories are those considered as such in the project documentation. Commits in all branches are considered. A file is 'touched' by a commit if its content or its path are modified by the commit. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as three calendar months period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • ( )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < ≤ 2 < ≤ 3 < ≤ 4 < ≤ 5

  • File stability index ( SCM_STABILITY_3M )

    Provided by: No provider defined!

    Used by:

    Scale: 1 < 3.79487179487 ≤ 2 < 1.4430952381 ≤ 3 < 1.14285714286 ≤ 4 < 1 ≤ 5

    Average number of commits touching each file in source code management repositories dated during the last three months.

    Source code management repositories are those considered as such in the project documentation. Commits in all branches are considered. A file is 'touched' by a commit if its content or its path are modified by the commit. Date used for each commit is 'author date' (when there is a difference between author date and committer date). Time range is measured as three calendar months period starting the day before the data retrieval (example: if retrieval is on Feb 3rd, period is from Jan 3rd to Feb 2nd, both included).


Page generated by Alambic 3.2 on Sun Feb 19 16:30:59 2017.