Release notes for Gerrit 2.8.4

If commitWithin was set to a low value, it caused poor performance when running the Reindex program on sites with a large amount of changes.

The commitWithin setting is now disabled from within Reindex by overriding the configuration with -1. Index updates are auto-flushed but not auto-committed, which is the least safe but the most efficient for reindexing the entire site.

SubIndex.NrtFuture objects were being added as listeners of searchManager and never released.

The "Expand All" and "Collapse All" settings now work like they did on the old change screen.

The patch file download does not work for commits with more than one parent (i.e. merges) and results in an error being displayed. Now the link is not shown for merge commits; a solution for merge patches will be investigated for future releases.

Regular branches like refs/heads/stable/ will now be displayed as just stable in the suggestion list when cherry-picking a change in the Web UI.

The "Save" button was not being disabled, and could be pressed multiple times while the message was being saved, resulting in multiple new patch sets being created.

In the new change screen, if the user clicked on a binary file in the file list, the unified view was used. Then when navigating to a previous or next file that is not binary, the diff view stayed in the old unified setting.

The whole "skipped xxx common lines" text is now a link, rather than just the number.

In the top right corner of a file the navigation cluster has a tooltip on the up arrow but did not show the tooltip on the left or right arrows.

Add missing @ExtensionPoint in ChangeListener so implementors can use @Listen to register.

Plugins could be built, but not loaded, if they had any manifest entries that contained a dollar sign.

When pushing changes it is easy to make a typo in the refspec and in this case new branches should not be created. If administrators want to create branches by push they should explicitly assign themselves the needed access rights.

The project list was being refreshed on every key event even if the filter did not change, e.g. moving the cursor inside the text entry was causing the list to update unnecessarily.

It is now possible to configure the default thread pool size, the size of the thread pool for sending emails, and the SMTP server connection timeout.

The project list screen was taking a long time to render over a large amount of projects (1,000+) and with even larger number of projects (3,000+), it could make the browser unresponsive.

The project list screen now uses pagination to resolve this issue. The number of projects displayed is determined by the Maximum Page Size user preference.

Option S is added to the projects REST API to support query offset.

If a group contains more than addreviewer.maxWithoutConfirmation members, adding it as reviewer to a change requires a confirmation. A user should only be asked for the confirmation when reviewers are added from the Web UI but not when the set-reviewers SSH command is used.

When using the Web UI (both old and new change screens) to cherry-pick a change to a branch that already has this change (e.g. cherry-picking on the same branch to get rid of dependencies), the corresponding patchset-created event had its patchSet.uploader set to the change’s owner instead of the current user. It is now set to the current user, so stream-events consumers can properly detect who uploaded the rebased patch set.

The setup documentation is updated to mention that there is no need to use latin1 encoding if you are using an engine other than MyISAM.