Preserve all version fields (#286)

Up to now extra version fields were ignored: only name and date fields were accepted. This changes that by retaining the full JSON data when reading the file, making it possible in the future to support custom fields.

This also fixes a bug with versions having released on the same date: they was not ordered as expected (reverse order).

releases/angularjs.json

@@ -164,14 +164,14 @@
       "name": "1.5.2",
       "date": "2016-03-18"
     },
-    "1.4.10": {
-      "name": "1.4.10",
-      "date": "2016-03-16"
-    },
     "1.5.1": {
       "name": "1.5.1",
       "date": "2016-03-16"
     },
+    "1.4.10": {
+      "name": "1.4.10",
+      "date": "2016-03-16"
+    },
     "1.5.0": {
       "name": "1.5.0",
       "date": "2016-02-05"
@@ -220,14 +220,14 @@
       "name": "1.4.3",
       "date": "2015-07-15"
     },
-    "1.3.17": {
-      "name": "1.3.17",
-      "date": "2015-07-06"
-    },
     "1.4.2": {
       "name": "1.4.2",
       "date": "2015-07-06"
     },
+    "1.3.17": {
+      "name": "1.3.17",
+      "date": "2015-07-06"
+    },
     "1.4.1": {
       "name": "1.4.1",
       "date": "2015-06-16"
@@ -272,14 +272,14 @@
       "name": "1.3.8",
       "date": "2014-12-19"
     },
-    "1.2.28": {
-      "name": "1.2.28",
-      "date": "2014-12-15"
-    },
     "1.3.7": {
       "name": "1.3.7",
       "date": "2014-12-15"
     },
+    "1.2.28": {
+      "name": "1.2.28",
+      "date": "2014-12-15"
+    },
     "1.3.6": {
       "name": "1.3.6",
       "date": "2014-12-09"
@@ -364,10 +364,6 @@
       "name": "1.2.11",
       "date": "2014-03-26"
     },
-    "1.2.10": {
-      "name": "1.2.10",
-      "date": "2014-01-27"
-    },
     "1.2.9": {
       "name": "1.2.9",
       "date": "2014-01-27"
@@ -376,6 +372,10 @@
       "name": "1.2.8",
       "date": "2014-01-27"
     },
+    "1.2.10": {
+      "name": "1.2.10",
+      "date": "2014-01-27"
+    },
     "1.2.7": {
       "name": "1.2.7",
       "date": "2014-01-07"