Document the new `is:merge` operator in release notes
Change-Id: I6381be9f304e53869b9311a276658b53c3adb9a3
diff --git a/pages/site/releases/3.2.md b/pages/site/releases/3.2.md
index c6aeea3..cf41bca 100644
--- a/pages/site/releases/3.2.md
+++ b/pages/site/releases/3.2.md
@@ -50,11 +50,22 @@
java -jar gerrit.war init -d site_path
```
+The changes index version has been increased. To run off-line reindexing of
+the changes (optional):
+
+```sh
+ java -jar gerrit.war reindex --index-name changes -d site_path
+```
+
+By default the changes index is automatically rebuilt upon the Gerrit startup
+after the upgrade.
+
**PERFORMANCE WARNING**: The migration process performs the cleanup of
the zombie draft comments in the All-Users.git repository that have been
left behind since the introduction of NoteDb. It is highly recommended
to perform a `git gc --aggressive` of the All-Users.git repository *BEFORE*
-running the migration.
+running the migration. Also the reindex of all the changes can take a
+significant amount of time for large-scale installations.
Also, make sure that the All-Users.git resides on
a fast access local filesystem for minimizing the migration time.
@@ -76,6 +87,16 @@
schema upgrade. To deny reverts, Gerrit administrators should remove this permission
from `All-Projects` ACL.
+### New is:merge merge operator for searching changes
+
+Introduce the new `is:merge` operator for allowing to find changes that are
+merge commits. This change requires a full reindex of the changes, which may take
+quite a long time to compute for large-sized installations.
+
+When choosing the on-line reindexing option (default) Gerrit can still operate
+with the old index version, disabling the `is:merge` operator until the new index
+has been successfully rebuilt.
+
### PolyGerrit UI
The Gerrit frontend has been migrated from Polymer 2 to
