updated CHANGELOG

CHANGELOG

@@ -9,6 +9,10 @@ v2.8.0 (XXXX-XX-XX)
 
 * fixes for AQL optimizer and traversal
 
+* randomly shuffle available V8 contexts when picking one for an HTTP or scheduler
+  task. This distributes requests more evenly across contexts so they can eventually
+  be garbage-collected.
+
 
 v2.8.0-beta2 (2015-12-16)
 -------------------------
@@ -299,9 +303,42 @@ v2.8.0-alpha1 (2015-12-03)
   re-enabled by explicitly setting the option `returnBodyOnError` to `false` (#1437)
 
 
+v2.7.4 (XXXX-XX-XX)
+-------------------
+
+* randomly shuffle available V8 contexts when picking one for an HTTP or scheduler
+  task. This distributes requests more evenly across contexts so they can eventually
+  be garbage-collected.
+
+* added the following attributes to the result of `collection.figures()` and the
+  corresponding HTTP API at `PUT /_api/collection/<name>/figures`:
+
+  - `documentReferences`: The number of references to documents in datafiles
+    that JavaScript code currently holds. This information can be used for
+    debugging compaction and unload issues.
+  - `waitingFor`: An optional string value that contains information about
+    which object type is at the head of the collection's cleanup queue. This 
+    information can be used for debugging compaction and unload issues.
+  - `compactionStatus.time`: The point in time the compaction for the collection
+    was last executed. This information can be used for debugging compaction
+    issues.
+  - `compactionStatus.message`: The action that was performed when the compaction
+    was last run for the collection. This information can be used for debugging
+    compaction issues.
+
+  Note: `waitingFor` and `compactionStatus` may be empty when called on a coordinator
+  in a cluster.
+
+* the compaction will now provide queryable status info that can be used to track
+  its progress. The compaction status is displayed in the web interface, too.
+
+
 v2.7.3 (2015-12-17)
 -------------------
 
+* fixed some replication value conversion issues when replication applier properties
+  were set via ArangoShell
+
 * fixed disappearing of documents for collections transferred via `sync` or
   `syncCollection` if the collection was dropped right before synchronization 
   and drop and (re-)create collection markers were located in the same WAL file