diff --git a/253b000de62a63feeeddd835fb57602f8568a696 b/253b000de62a63feeeddd835fb57602f8568a696
new file mode 100644
index 0000000..ebe5f4b
--- /dev/null
+++ b/253b000de62a63feeeddd835fb57602f8568a696
@@ -0,0 +1,55 @@
+{
+  "comments": [
+    {
+      "key": {
+        "uuid": "ae564743_77254303",
+        "filename": "Purtle.php",
+        "patchSetId": 1
+      },
+      "lineNbr": 8,
+      "author": {
+        "id": 128
+      },
+      "writtenOn": "2016-05-02T10:14:41Z",
+      "side": 1,
+      "message": "I\u0027d prefer not to do have the patch level here. According to SemVer semantics, It has no impact on compatibility. So it does not gain us anything, and it\u0027s a hassle to maintain.",
+      "revId": "253b000de62a63feeeddd835fb57602f8568a696",
+      "serverId": "e9e9afe9-4712-486d-8885-f54b72dd1951",
+      "unresolved": false
+    },
+    {
+      "key": {
+        "uuid": "ae564743_176de72d",
+        "filename": "RELEASE-NOTES.md",
+        "patchSetId": 1
+      },
+      "lineNbr": 0,
+      "author": {
+        "id": 128
+      },
+      "writtenOn": "2016-05-02T10:14:41Z",
+      "side": 1,
+      "message": "I don\u0027t think this is necessary. The purpose of release notes is to document changes to the interface, not every bug fix. I suppose it\u0027s good to track major bug fixes. \n\nAnyway, no problem here, just saying ;)",
+      "revId": "253b000de62a63feeeddd835fb57602f8568a696",
+      "serverId": "e9e9afe9-4712-486d-8885-f54b72dd1951",
+      "unresolved": false
+    },
+    {
+      "key": {
+        "uuid": "ae564743_777c23e3",
+        "filename": "composer.json",
+        "patchSetId": 1
+      },
+      "lineNbr": 27,
+      "author": {
+        "id": 128
+      },
+      "writtenOn": "2016-05-02T10:14:41Z",
+      "side": 1,
+      "message": "why?",
+      "revId": "253b000de62a63feeeddd835fb57602f8568a696",
+      "serverId": "e9e9afe9-4712-486d-8885-f54b72dd1951",
+      "unresolved": false
+    }
+  ]
+}
\ No newline at end of file