From 2f4de215066f65a88e823bdf5ccfa326afc215a9 Mon Sep 17 00:00:00 2001 From: Sverre Rabbelier Date: Wed, 18 Jun 2008 23:42:43 +0200 Subject: [PATCH] Extended the description of the 'branch contains' metric We will be trying to determine in how much a commit belongs to a certain branch. In other words, we want to find out if a commit was made 'on' a certain branch, or merely 'merged in'. --- doc/metrics.txt | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/doc/metrics.txt b/doc/metrics.txt index 20650c5..c7ab3fa 100644 --- a/doc/metrics.txt +++ b/doc/metrics.txt @@ -7,10 +7,15 @@ The following metrics will be used to determine if something is a fix: mainstream branch at the point of a release, as such there has to be a lower limit (say, the 'creation point' of the branch) from where on commits are seen as 'part of - the maintenance branch'. This means that when specifying - which branches are matches not only the branch name - should be specified, but also the starting commit. - + the maintenance branch'. This means that we need a + mechanism to determine whether a commic belongs on a + branch or not. This can be done by determining how + 'dilated' the commit is at the head of a branch. Here we + define 'dilating' as merging, if a commit is part of a + branch only because it got merged in, that is a strong + dilation. If another branch is merged in that is only a + slight dilation (or perhaps none at all). + * If the commit message matches a certain regexp. For example, if the commit message contains the line: -- 2.11.4.GIT