update NEWS & CHANGES
More efficient view updates

In several scenarios the writer process of the view
updater was collecting very small batches of map
values, which is not optimal regarding efficiency.
This change ensures the batches are larger by queing
batches of map values into the writer's queue instead
of queing map values one by one.
This queing behaviour was changed by COUCHDB-1186 and
its non-optimal efficiency for certain documents/map
functions wasn't noticed before.
[docs] compression is enabled by default and bumps on-disk version

- updated NEWS and CHANGES
Whitespace
Add 100ms sleep to etap:end_tests() to prevent hanging

It's not clear if the issue is etap, escript, prove, or couchdb. This
needs further investigation.

Jira-1424
update NEWS and CHANGES
Fix very slow test test/etap/220-compaction-daemon.t

After the recent change in the view updater that ensures
the view updater's writer process collects larger batches
of map values to write into the index, the test's desired
fragmentation of 70% takes much more time to happen.
To fix this, simply decreased the target fragmentation.

(patch by Filipe)
Fix view etag calculation regression introduced by fb7225

The optimisation relied on creating batches of documents to be
sent to the view server. The implementation created the batch
in a foldl function instead of a foldr function causing the
wrong update sequence to be persisted because the write assumes
the last item in the list to have the largest sequence.

Thanks to Filipe for guiding the research.
[docs] bring README, THANKS, AUTHORS up to date for 1.2.0

- correct Firefox test suite usage notes
- add jhs@
COUCHDB-1426 Ensure use of specified SpiderMonkey

There were a few bugs in configuration settings when users specified
--with-js-include and --with-js-lib for custom SpiderMonkey
installations when a SpiderMonkey library is installed globally. This
patch addresses this by reordering configuration checks to use the
specified variables without adding information from pkg-config checks or
from default settings.

There is also a new setting --with-js-lib-name which is required due to
SpiderMonkey having so many names for its libraries. If configuration or
building fails the most likely scenario is that it picked up an older
installed SpiderMonkey in the library search path. To fix you should
only need to add --with-js-lib-name with the value that should be passed
to the linker. Ie, -lfoo would be set as "--with-js-lib-name=foo".
remove unnecessary eaccess special casing

It's better to let these errors bubble and/or not give them special
treatment when file:format_error/1 can do a better job of describing
the failure.
clear ETS table entry if view group fails to start

Without this, the next process which tries to open the view group
will add itself to the wait list even though the monitor has already
fired. When that happens, the caller hangs forever.
don't delete view groups that fail to open

...but log a message instead. Fixes COUCHDB-1445.
update NEWS and CHANGES for COCUHDB-1445
Fix error stack traces

If you get the stack in an exception handler after calling a function it
gets changed from where the exception was thrown. Fixed simply by
grabbing the stack before making logging calls.
Add note about logging correct stacktrace
restore some log messages after 04c4a10
Updated NEWS and CHANGES for 29eac043
Removed superfluous line from NEWS
Receive the correct error message to proceed upon ignoring a file-open error