diff --git a/ChangeLog b/ChangeLog
index 3b1c493..bba5fe7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1 +1,181754 @@
-ChangeLog is maintained by "git log".
+commit f453425865d7151f27cd43c4c1e96919ec25a4f8
+Author: Niels de Vos <ndevos@redhat.com>
+Date:   Thu May 11 12:00:10 2017 +0200
+
+    doc: release-notes for GlusterFS-3.8.12
+    
+    BUG: 1440754
+    Change-Id: I6602046ddc12834384e11c41a6e8e0cb7a8d5d71
+    Signed-off-by: Niels de Vos <ndevos@redhat.com>
+    Reviewed-on: https://review.gluster.org/17252
+    Smoke: Gluster Build System <jenkins@build.gluster.org>
+    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
+    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
+    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
+
+commit ae2f6a650fab30a91357c3f3327a432a0edb5fdf
+Author: Raghavendra G <rgowdapp@redhat.com>
+Date:   Fri Apr 11 15:58:47 2014 +0530
+
+    performance/read-ahead: prevent stale data being returned to application.
+    
+    Assume that fd is shared by two application threads/processes.
+    
+    T0 read is triggered from app-thread t1 and read call passes through
+       write-behind.
+    T1 app-thread t2 issues a write. The page on which read from t1 is
+       waiting is marked stale
+    T2 write-behind caches write and indicates to application as write
+       complete.
+    T3 app-thread t2 issues read to same region. Since, there is already a
+       page for that region (created as part of read at T0), this read
+       request waits on that page to be filled (though it is stale, which
+       is a bug).
+    T4 read (triggered at T0) completes from brick (with write still
+       pending). Now both read requests from t1 and t2 are served this data
+       (though data is stale from app-thread t2's perspective - which is a
+       bug)
+    T5 write is flushed to brick by write-behind.
+    
+    Fix is to not to serve data from a stale page, but instead initiate a
+    fresh read to back-end.
+    
+    >Change-Id: Id6af733464fa41bb4e81fd29c7451c73d06453fb
+    >BUG: 1414242

More commit messages for this ChangeLog can be found at
https://forge.gluster.org/glusterfs-core/glusterfs/commits/v3.8.12
