Release notes for Gerrit 2.3

Adds draft status to Change. DRAFT status in change occurs before NEW and will be for a change that is not meant for review (yet). Also adds magic branches refs/drafts/ and refs/publish/ that will handle whether or not a patchset is a draft or goes straight to review. refs/for/ should be deprecated in favor of explicitly marking a patchset as a draft or directly to review.

If a patchset is a draft, adds a (DRAFT) label next to the revision (or gitweb link if it exists). If a change is a draft, adds a (DRAFT) next to the subject and changes the status appropriately.

Adds Publish button to draft patchsets in UI and an option to publish draft patchsets in the review ssh command. Publishing a draft patchset makes it visible. Publishing a draft patchset in a draft change irreversibly upgrades the change status to NEW.

Adds ability to delete draft changes and patchsets that are not meant or fit for code review. Deleting a draft patchset also deletes the corresponding ref from the repository and decrements the next patch set number for the change if necessary. Deleting a draft change deletes all of its (draft) patchsets.

Pushing to refs/drafts/ will now push a draft patchset. If this is the first patch set, change created will be in draft status. Pushing a draft patchset to a draft change keeps it in draft status. Pushing a non-draft patchset (with refs/publish/ or refs/for/, they do the same thing) to a draft change turns it into a non-draft change. Draft patchsets cannot be submitted.

Add a new panel in the Admin→Projects Screen. It enables the users that are allowed to create projects via command-line to create them also via web interface.

Add a list of parent suggestions for create project in the UI, so the user can select a parent for the new project from a list of projects that are already parents to other projects.

Don’t show … skipping 1 common line …. The text to show this takes up just as much space as showing the line which was skipped.

Allow lines of context which were skipped in the side-by-side diff view to be expanded. This makes it easier to get more code context when needed but not show huge amounts of unneeded data.

Allows listing of projects together with their respective description.

Add a new option --all to the ls-projects SSH command to display all projects that are accessible by the calling user account. Besides the projects that the calling user account has been granted READ access to, this includes all projects that are owned by the calling user account (even if for these projects the READ access right is not assigned to the calling user account).

Add an option --suggest-parents which will print out a list of projects that are already parents to another projects, thus it can help user to find a suitable parent for the new project.

This change adds a new option to the set-project-parent command that allows reparenting all child projects of one parent project to another parent project.

Add an option to the ls-groups SSH command that allows to list only those groups for which any permission is assigned to a project.

Allows user to list files and attributes (ADDED, MODIFIED, DELETED, RENAMED, COPIED) when querying for patch sets.

"--force-message" option for the SSHD review command, which allows Gerrit to publish the "--message", even if the labels could not be applied due to change being closed.

Active state indicates the project is regular and is the default value.

Read Only means that users can see the project if read permission is granted, but all modification operations are disabled.

Hidden means the project is not visible for those who are not owners

Gerrit treats user names as case sensitive, while some LDAP servers don’t. On first login to Gerrit the user enters his user name and Gerrit queries LDAP for it. Since LDAP is case-insensitive with regards to the username, the LDAP authentication succeeds regardless in which case the user typed in his user name. The username is stored in Gerrit exactly as entered by the user. For further logins the user always has to use the same case. If the user specifies his user name in a different case Gerrit tries to create a new account which fails with "Cannot assign user name … to account …; name already in use.". This error occurs because the LDAP query resolves to the same LDAP user and storing the username for SSH (which is by default always lower case) fails because such an entry exists already for the first account that the user created.

This change introduces a new configuration parameter that converts the user name always to lower case before doing the LDAP authentication. By this the login to the Gerrit WebUI gets case insensitive. If this configuration parameter is set, the user names for all existing accounts have to be converted to lower case. This change includes a server program to do this conversion.

A new configuration parameter is introduced that converts the username that is received to authenticate a git operation to lower case for looking up the user account in Gerrit.

By setting this parameter a case insensitive authentication for the git operations can be achieved, if it is ensured that the usernames in Gerrit (scheme username) are stored in lower case (e.g. if the parameter ldap.accountSshUserName is set to ${sAMAccountName.toLowerCase}).

This helps prevent a very slow LDAP server from blocking all SSH command creation threads.

This limits the size of uploaded files

Previously the link to the external gitweb-type pages said "(gitweb)" regardless if using cgit or a custom service.

These features are: user agent detection and automatic refresh logic associated with the site header, footer and CSS.

This only seems to matter to IntelliJ, since the Main class is provided to the war via an overlay in gerrit-war/pom.xml

Fixes java.lang.NoClassDefFoundError: com/google/gwt/dev/DevMode

The feature introduced in this release allows superprojects to subscribe to submodules updates.

When a commit is merged to a project, the commit content is scanned to identify if it registers submodules (if the commit contains new gitlinks and .gitmodules file with required info) and if so, a new submodule subscription is registered.

When a new commit of a registered submodule is merged, gerrit automatically updates the subscribers to the submodule with new commit having the updated gitlinks.

The most notable benefit of the feature is to not require to push/merge commits of super projects (subscribers) with gitlinks whenever a project being a submodule is updated. It is only required to push commits with gitlinks when they are created (and in this case it is also required to push .gitmodules file).

When linking a new user identity to an existing account, permit the Realm to observe the new incoming identity and the current account, and to alter the request. This enables a Realm to observe when a user verifies a new email address link.

When a change is published via the cherry-pick merge strategy, show the final commit as a patchset in the change history. This now makes it possible to search for the cherry-picked SHA1.

If some change was abandoned but later submitted (e.g. by cherry-picking it to a another branch) then pushing a new branch that contains this change no longer adds a new comment.

Always update the href of the Sign In anchor in the menu bar with the current page URL after /login/, making the redirect process bring users back to the current view after sign in.