An analysis task should be closed if a progression cause is identified

[WebKit.git] / Websites / perf.webkit.org / ChangeLog

diff --git a/Websites/perf.webkit.org/ChangeLog b/Websites/perf.webkit.org/ChangeLog
index 4ec2ff7..8611b1d 100644 (file)
--- a/Websites/perf.webkit.org/ChangeLog
+++ b/Websites/perf.webkit.org/ChangeLog
@@ -1,3 +1,23 @@
+2016-03-17  Ryosuke Niwa  <rniwa@webkit.org>
+
+        An analysis task should be closed if a progression cause is identified
+        https://bugs.webkit.org/show_bug.cgi?id=155549
+
+        Reviewed by Chris Dumez.
+
+        Since a progression is desirable, we should close an analysis task once its cause is identified.
+
+        Also fix some typos.
+
+        * init-database.sql: Fixed a typo.
+        * public/api/analysis-tasks.php:
+        * public/v3/models/analysis-task.js:
+        (AnalysisTask.prototype.dissociateBug): Renamed from dissociateBug.
+        * public/v3/pages/analysis-task-page.js:
+        (AnalysisTaskPage.prototype.render):
+        (AnalysisTaskPage.prototype._dissociateBug): Renamed from _dissociateBug.
+        (AnalysisTaskPage.prototype._dissociateCommit): Fixed the typo in the alert.
+
 2016-03-16  Ryosuke Niwa  <rniwa@webkit.org>
 
         Analysis task page should allow specifying commits that caused or fixed a regression or a progression