### Core

- The following architectures have been obsoleted: linuxkcc, alphakcc, linuxia64sgi, linuxdeb2ppc, solariskcc, sgikcc and linuxpgcc.
- All of ROOT (not just Core) has been checked by a very nice static code analyzer coverity, see: http://www.coverity.com/. Many of the reports have been fixed. We expect that this further increases the stability of ROOT.
- Add support for 'Dump' and 'Browse' of 'emulated' object.
- TBits equality operator nows return true if the 2 operands have different length and all the bits in the longer TBits that are passed the length of the shorter TBits are zero (i.e. the default value of each bits is zero).
- Properly handle scripts with line longer than 1024 characters.
- Repair the handling of ACLiC options on the command line (for example a.C+g).
- In TClass::BuildEmulatedRealData properly handle the case of TNamed member that are not base class.
- On the command line:
  - Fix the tab-completion of filenames in the sub-directories.
  - Prevent the unadvertent replacement of an arrow with a dot when the left side is actually a pointer
- More user friendly stacktrace in case of a crash, with hints where the problem might be. On Linux and MacOS X these stacktraces are generated by the script $ROOTSYS/etc/gdb-backtrace.sh. Using the Root.StackTraceMessage resource one can customize the message printed by the script. The entire script can be replaced using the Root.StacktraceScript resource.
- Numerous minor bug fixes...

#### New module `editline`

The new module `editline` enhances the prompt, giving type and syntax feedback using e.g. colors. Class names are highlighted blue when typed, indicating that it is known to ROOT. Matching parenthesis pairs are highlighted green when typed, or when the cursor is moved to a bracket. This works for () {} and [] brackets. Any mismatched brackets (those without a matching partner) will be highlighted red when typed or when the cursor is moved to the bracket. Tab completion output is colored magenta to differentiate between tab completion output and user input.

All of the colors are configurable in the `.rootrc` file. They can be specified as #rgb or #rrggbb or color names: black, red, green, yellow, blue, magenta, cyan or white. They can be followed by an optional `bold` (alias `light`) or `underlined`. `Rint.ReverseColor` allows to quickly toggle between the default "light on dark" (`yes`) instead of "dark on light" (`no`), depending on the terminal background.

An example configuration would be:

    Rint.TypeColor:           blue
    Rint.BracketColor:        bold green
    Rint.BadBracketColor:     underlined red
    Rint.TabColor:            magenta
    Rint.PromptColor:         black
    Rint.ReverseColor:        no

The enhanced prompt is available on all platforms with [n]curses, including Linux, Solaris and MacOS; the bold and underline options are available also for black and white terminals. You can `export` (or `setenv`) `TERM=xterm-256color` for nicer colors.

With editline comes also an improved terminal input handler. It supports e.g. ^O (Ctrl-o) to replay the history: suppose you have entered

    ...
    root [3] i = func()
    root [4] i += 12
    root [5] printf("i is %d\n", i)

You now want to re-run these three lines. As always, you press the up cursor three times to see

    root [6] i = func()

and now press ^O (Ctrl-o) to run the line, and prepare the next line:

    root [6] i = func()^O
    root [7] i += 12^O
    root [8] printf("i is %d\n", i)^O
    root [9]

allowing you to re-run that part of the history without having to press the up-arrow again and again.

Currently, `editline` is disabled on Windows.