Release notes for Gerrit 2.11

The commit message is now edited using the inline edit feature.

Using the Rebase button it is now possible to rebase a change onto a different change (on the same destination branch), rather than only onto the head of the destination branch or the latest patch set of the predecessor change.

Header files are now listed before implementation files.

The Show Change Sizes As Colored Bars In Changes Table setting is renamed to Show Change Sizes As Colored Bars and is now used to also control how the change size is shown per file in the file table.

When enabled (which is the default), the change size per file is shown as a sum of lines added/removed, and also representated by a colored bar showing the proportion of added/removed lines.

When disabled, the colored bar is not shown and the change size per file is shown in the same way as it used to be in the old change screen.

The setting determines whether or not the diff table header with the patch set selection should be automatically hidden when scrolling down more than half of a page.

Search results in vim mode are highlighted in the scrollbar with gold colored annotations.

The button creates a new change on the refs/meta/config branch and opens the project.config file in the inline editor.

This allows project owners to easily edit the project.config file from the browser, which is useful since it is possible that not all configuration options are available in the UI.

In the past, Gerrit bugs, lack of transactions, and unreliable NoSQL backends have at various times produced a bewildering variety of corrupt states.

This endpoint can be used to detect, explain, and repair some of these possible states of a change.

The audit log service allows to register listeners to group member added and group member deleted events. A default listener logs these events to the database as before, but additional listeners may now be registered for these events using the GroupMemberAuditListener interface.

Plugins implementing the RefOperationValidationListener interface can perform additional validation checks against ref creation/deletion operations before they are applied to the git repository.

Plugins can provide sub-menu items within the Projects context. The ${projectName} placeholder is replaced by the project name.

When a plugin does not expose Guice Modules explicitly, auto discover and register static/init.js as WebUi extension if found by the plugin content scanner.

Plugins implementing OutgoingEmailValidationListener interface can filter and modify outgoing emails before they are sent.

This allows, for example, to write a plugin that can import a project including review information from another Gerrit server.

In the file table, parts of the file path that are common to the file previously listed are muted. The purpose of this is to make it easier to see files that all belong under the same path, but some users find it annoying.

This feature can now be enabled or disabled, per user, with the Mute Common Path Prefixes In File List setting.

Typing LGTM in the review cover message no longer automatically selects the highest available Code-Review score.

Previously there was no confirmation and a draft change or revision patch set would be lost if the button was accidentally clicked.

Several improvements have been made:

When a cherry-pick operation failed with Cherry pick failed error, there was no way to know the reason for the failure: merge conflict or the commit is already on the target branch. These failures are now differentiated and an appropriate error is reported.

If there were several users with long user names with the same prefix, e.g. AutomaticGerritVoterLinux and AutomaticGerritVoterWindows, they would both be shown as AutomaticGerritVo… and users had to expand the comment to see the full user name.

The ellipsis is now inserted in the middle of the user name so that the start and end of the user name are always visible, e.g. AutomaticG…VoterLinux and AutomaticG…terWindows.

Chrome for Android has Font Boosting, which caused the review comments to be displayed too large.

If a change owner voted on a change, it was not possible for anyone other than the owner to remove the vote.

When a change is cherry-picked, the topic from the source change is preserved on the newly created change.

If a change from the Same Topic tab was clicked, the selected tab would reset to the default tab (Related Changes).

Under some circumstances the browser’s scrollbar would be shown over the copy-to-clipboard icons in the download dropdown.

In the reply box, the text of the label score is displayed on the right hand side when a score is selected, but this was missing for simple boolean labels.

When matching accounts by email address against an external account, results now show the email address that matched, not the preferred email address.

Previously it would remain in visual mode.

cpp and hpp files were sometimes rendered with C mode and not the extended C++ mode. This prevented keywords like class from being colored by the highlighter.

The Exclusive checkbox was not aligned with the other checkboxes.

The endpoint can now be used by any user who has visibility of the change.

The behavior was inconsistent with the documentation. In the default case it was including only the account name, rather than only the account ID.

The ref of a revision was only returned as part of the fetch info, which is only available if the download commands are installed.

When the change.allowDrafts setting is False, it is not allowed to delete draft changes or patch sets.

In this case the response 405 Method Not Allowed is now returned, instead of 409 Conflict.

Deleting multiple branches from the UI was resulting in a server error when branches were in the packed-refs.

The projects REST API documentation states that the .git suffix will be stripped off the input project name, if present.

This was working for the Create Project endpoint, but not for any of the others.

Previously createMissingRepositories = false would prevent the replication plugin from trying to create a new project when a ref-updated event was fired, but when a project-created event was fired the replication plugin would try to create a project on the remote.