<commit_before>#Defect Resolution Trend

This chart shows a traditional arrival kill rate during the release period
selected.  It does not care whether defects are associated with the release
directly, only that they were created during the time period.

* Note that items might have been killed during the period, but if those are
items that were created before the period started, they do not count.

An additional Trend line has been added that shows the difference between the
number that have been created (arrived) and killed (resolved) to the date.  
The ideal here is for resolving defects to happen as fast or faster than creating
new ones, so a rising line is suboptimal, a flat or declining line is better.


## Development Notes

* Whether an item is a production item is based on the existence of at least
one value in the incidents field, which is a web link field.
* Because it's a web link field, we can't query on it and the data isn't in 
lookback, so we have to go get all the defects first.


### First Load

If you've just downloaded this from github and you want to do development, 
you're going to need to have these installed:

 * node.js
 * grunt-cli
 * grunt-init
 
Since you're getting this from github, we assume you have the command line
version of git also installed.  If not, go get git.

If you have those three installed, just type this in the root directory here
to get set up to develop:

  npm install

### Structure
<commit_msg>update README to remove kill language<commit_after>#Defect Resolution Trend

This chart shows the rate of items created and resolved during the release period
selected.  It does not care whether defects are associated with the release
directly, only that they were created during the time period.

* Note that items might have been resolved during the period, but if they are
items that were created before the period started, they do not count.

An additional Trend line has been added that shows the difference between the
number that have been created and killed to the date.  The ideal here is for resolving 
defects to happen as fast or faster than creating new ones, so a rising line is 
suboptimal, a flat or declining line is better.

There is an app setting to let the installer decide whether the app will count all
defects or only defects associated with production via a special web link field.

## Development Notes

* Whether an item is a production item is based on the existence of at least
one value in the incidents field, which is a web link field.
* Because it's a web link field, we can't query on it and the data isn't in 
lookback, so we have to go get all the defects first.


### First Load

If you've just downloaded this from github and you want to do development, 
you're going to need to have these installed:

 * node.js
 * grunt-cli
 * grunt-init
 
Since you're getting this from github, we assume you have the command line
version of git also installed.  If not, go get git.

If you have those three installed, just type this in the root directory here
to get set up to develop:

  npm install

### Structure

{'fraction_non_alphanumeric': 0.03380553766902769, 'fraction_numerical': 0.0, 'mean_word_length': 3.987158908507223, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4311762', 'n_tokens_mistral': 797, 'n_tokens_neox': 750, 'n_words': 526}