issue2550648 - partial fix for problem in this issue. Ezio Melotti reported that the expression editor allowed the user to generate an expression using retired values. To align the expression editor with the simple dropdown search item, retired values are now removed from the expression editor. Do we really want this though? Supposed a keyword is retired and I want to search for an issue with that retired keyword? Do we have a best policy document that says to remove retired keywords from all places it could possibly be used? It could be argued that the simple search dropdown is wrong and should allow selecting retired values.

# 3rd party libraries for some of the trackers

The files in theis directory are the sources for files that are used
by the trackers and optional functionality. It includes unminified
javascript and source files used to generate javscript and css.

## Bootstrap

To build Boostrap, install [nodejs](http://nodejs.org/) and then do
the following -

```
$ sudo npm install -g connect@2.1.3 hogan.js@2.0.0 jshint@0.9.1 recess@1.1.9 uglify-js@1.3.4
$ make build
```

The files are now located in docs/assets