blob: 69578278733c60f1a72aa5d7efecbd4d76db42f4 [file] [log] [blame]
Yuxuan 'fishy' Wang4f5ad9d2016-05-03 16:18:58 -07001= Release notes for Gerrit 2.11.5
David Pursehouse4cf1aae2015-10-29 16:42:06 +09002
3Gerrit 2.11.5 is now available:
4
5link:https://gerrit-releases.storage.googleapis.com/gerrit-2.11.5.war[
6https://gerrit-releases.storage.googleapis.com/gerrit-2.11.5.war]
7
8There are no schema changes from link:ReleaseNotes-2.11.4.html[2.11.4].
9
10
Yuxuan 'fishy' Wang4f5ad9d2016-05-03 16:18:58 -070011== Important Notes
David Pursehouse0c304912015-12-09 01:25:50 +000012
13*WARNING:* This release uses a forked version of buck.
14
15Buck was forked to cherry-pick an upstream fix for building on Mac OSX
16El Capitan.
17
18To build this release from source, the Google repository must be added to
19the remotes in the buck checkout:
20
21----
22 $ git remote add google https://gerrit.googlesource.com/buck
23----
24
25
Yuxuan 'fishy' Wang4f5ad9d2016-05-03 16:18:58 -070026== Bug Fixes
David Pursehouse4cf1aae2015-10-29 16:42:06 +090027
28* link:https://code.google.com/p/gerrit/issues/detail?id=3442[Issue 3442]:
29Handle commit validation errors when creating/editing changes via REST.
30+
31When an exception was thrown by a commit validator during creation of
32a new change, or during publish of an inline edit, this resulted in an
33internal server error message which did not include the actual reason
34for the error.
35
36* link:https://code.google.com/p/gerrit/issues/detail?id=3616[Issue 3616]:
37Strip trailing blank lines from commit messages when modified in the inline
38editor.
39+
40Blank lines were not trimmed from the end of commit messages, which caused
41problems when the commit was merged and then cherry-picked with the `-x`
42option (from the command line).
43
44* Tweak JS clipboard API integration to work on Firefox.
45+
46The JS 'copy' functionality was working on Chrome, but not on Firefox.
47
48* Use image instead of unicode character for copy button.
49+
50Some browsers were unable to render the unicode character.
51
52* Include server config module in init step.
53+
54This allows SecureStore to be used during plugins' init step.
55
56* link:https://code.google.com/p/gerrit/issues/detail?id=3659[Issue 3659]:
57Show inline comments in change screen history when inline edit is active.
58+
59It was not possible to see the inline comments in the history on the
60change screen when in edit mode.
61
62* Improve rendering of `stream-events` tasks in the `show-queue` output.
63+
64Entries for `stream-events` are now rendered as 'Stream Events (username)'.
65
66* link:https://code.google.com/p/gerrit/issues/detail?id=3655[Issue 3655]:
67Fix incorrect owner group matching behavior.
68+
69When the given group did not match any group, the group was matched
70on a group whose name starts with the argument, instead of throwing an
71error to notify the user.
72
73* link:https://code.google.com/p/gerrit/issues/detail?id=3664[Issue 3664]:
74Fix double slash on URL when switching account.
75+
76One too many slashes on the URL caused redirection back to the root
77page instead of the intended location.
78
79* link:https://code.google.com/p/gerrit/issues/detail?id=3666[Issue 3666]:
80Fix server error when commit validator is invoked on initial commit.
81+
82If a commit was uploaded for review as the first commit in a repository
83that was created with no initial empty commit, invoking a commit validator
84on the new commit would cause an internal error.
85
86* Replication plugin.
87
88** Parse replication delay and retry times as time units.
89+
90The replication delay and retry values were interpreted as seconds and
91minutes respectively, but were being parsed as integers.
92+
93This is inconsistent with how time units are handled in other Gerrit
94configuration settings, and can cause confusion when the user configures
95them using the time unit syntax such as '15s' and it causes the plugin
96to fail with 'invalid value'.
97+
98The delay and retry now are parsed as time units. The value can be given
99in any recognized time unit, and the defaults remain the same as before;
10015 seconds and 1 minute respectively.
101
102** Remove documentation of obsolete `remote.NAME.timeout` setting.