From f9e3870941127532bda26c67ac40a9f8d0248412 Mon Sep 17 00:00:00 2001
From: Raul Ochoa <rochoaf@gmail.com>
Date: Wed, 30 Sep 2015 00:59:42 +0200
Subject: [PATCH] Update news with all changes related to use Windshaft as
 library

---
 NEWS.md             | 34 +++++++++++++++++++++++++++++++++-
 npm-shrinkwrap.json |  2 +-
 package.json        |  2 +-
 3 files changed, 35 insertions(+), 3 deletions(-)

diff --git a/NEWS.md b/NEWS.md
index 8bfbdd7f..69e1c097 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -1,9 +1,41 @@
 # Changelog
 
-## 2.13.1
+## 2.14.0
 
 Released 2015-mm-dd
 
+Summary: this starts using Windshaft as library, it no longer extends old Windshaft server.
+
+New features:
+ - Named tiles: /api/v1/map/named/:name/:layer/:z/:x/:y.:format
+
+Ported from Windshaft pre-library:
+ - Almost all acceptance tests, some unit and some integration tests
+ - Stats + profiler
+
+New features:
+ - Named maps MapConfig provider
+ - Base controller with: req2params, send response/error mechanisms
+ - Authentication/Authorization moves to its own API so it can be reused
+ - Surrogate-Key headers for named maps and affected tables
+
+Improvements:
+ - No more fake requests to emulate map config instantiations
+ - As named maps previews are using named map MapConfigProvider it doesn't need to load the MapConfig
+ - Controllers using Windshaft's backends to request resources through MapConfig providers
+ - Express 4.x, as Windshaft no longer provides an HTTP server, here we start using latest major version of Express.
+ - assert.response implemented using request
+ - All tests validate there are no unexpected keys in Redis and keys requested to be deleted after a test are present
+ - Test suite in Makefile generated with `find`
+ - Image comparison with `mapnik.Image.compare`
+ - Doesn't emit Named map update event on unmodified templates
+
+TODO:
+  - Named map provider checks on every request if named map has changed to reload it (actually reset it so MapConfig has to be regenerated). See https://github.com/CartoDB/Windshaft-cartodb/commit/f553efa69e83fdf296154ab1b7b49aa08957c04e. This is done this way because when running the Service in a cluster there is no communication between different instances so when a named map gets updated in one of the them the rest is not aware/notified of the change. In the future there should be a mechanism to synch this changes between instance:
+   * endpoint
+   * redis pub/sub
+   * backdoor
+
 
 ## 2.13.0
 
diff --git a/npm-shrinkwrap.json b/npm-shrinkwrap.json
index ef74cc9c..7af181c5 100644
--- a/npm-shrinkwrap.json
+++ b/npm-shrinkwrap.json
@@ -1,6 +1,6 @@
 {
   "name": "windshaft-cartodb",
-  "version": "2.13.1",
+  "version": "2.14.0",
   "dependencies": {
     "body-parser": {
       "version": "1.14.1",
diff --git a/package.json b/package.json
index 3008bb9b..8212a930 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
     "private": true,
     "name": "windshaft-cartodb",
-    "version": "2.13.1",
+    "version": "2.14.0",
     "description": "A map tile server for CartoDB",
     "keywords": [
       "cartodb"