blob: 17192944563bc7889443e0267c05fd5ee65f76b8 [file] [log] [blame]
David Pursehouse429c79d2014-03-26 07:30:39 -07001Release notes for Gerrit 2.8.4
2==============================
3
4There are no schema changes from link:ReleaseNotes-2.8.3.html[2.8.3].
5
6Download:
7link:https://gerrit-releases.storage.googleapis.com/gerrit-2.8.4.war[
8https://gerrit-releases.storage.googleapis.com/gerrit-2.8.4.war]
9
10
11Bug Fixes
12---------
13
14
15Secondary Index
16~~~~~~~~~~~~~~~
17
18
19* Disable `commitWithin` when running Reindex.
20+
21If `commitWithin` was set to a low value, it caused poor performance
22when running the Reindex program on sites with a large amount of changes.
23+
24The `commitWithin` setting is now disabled from within Reindex by overriding
25the configuration with '-1'. Index updates are auto-flushed but not
26auto-committed, which is the least safe but the most efficient for reindexing
27the entire site.
28
29* Fix memory leak in Lucene index.
30+
31`SubIndex.NrtFuture` objects were being added as listeners of `searchManager`
32and never released.
33
34Change Screen
35~~~~~~~~~~~~~
36
37
38* link:https://code.google.com/p/gerrit/issues/detail?id=2456[Issue 2456]:
39Respect the comment visibility preference in the new change screen.
40+
41The "Expand All" and "Collapse All" settings now work like they did on
42the old change screen.
43
44* link:https://code.google.com/p/gerrit/issues/detail?id=2538[Issue 2538]:
45Don't show the "Patch File" download for merge commits.
46+
47The patch file download does not work for commits with more than one
48parent (i.e. merges) and results in an error being displayed. Now the
49link is not shown for merge commits; a solution for merge patches will
50be investigated for future releases.
51
52* link:https://code.google.com/p/gerrit/issues/detail?id=2526[Issue 2526]:
53Hide the `refs/heads/` prefix in branch suggestion list for cherry-picks.
54+
55Regular branches like `refs/heads/stable/` will now be displayed as
56just `stable` in the suggestion list when cherry-picking a change in the
57Web UI.
58
59* Disable the "Save" button after it is pressed when editing the commit
60message.
61+
62The "Save" button was not being disabled, and could be pressed multiple
63times while the message was being saved, resulting in multiple new patch
64sets being created.
65
66* Fix syntax highlighting for shell files in new side-by-side diff.
67
68* Fix inconsistent behavior of diff view when viewing binary files.
69+
70In the new change screen, if the user clicked on a binary file in
71the file list, the unified view was used. Then when navigating to
72a previous or next file that is not binary, the diff view stayed in
73the old unified setting.
74
75* Make the skip bar more user friendly in side-by-side diff.
76+
77The whole "skipped xxx common lines" text is now a link, rather
78than just the number.
79
80* Show previous and next file shortcut keys in new side-by-side
81navigation arrow tooltips.
82+
83In the top right corner of a file the navigation cluster has a
84tooltip on the up arrow but did not show the tooltip on the left
85or right arrows.
86
87Plugins
88~~~~~~~
89
90
91* Fix ChangeListener auto-registered implementations.
92+
93Add missing `@ExtensionPoint` in `ChangeListener` so implementors can
94use `@Listen` to register.
95
96* Escape dollar sign in plugin manifest entries.
97+
98Plugins could be built, but not loaded, if they had any manifest entries
99that contained a dollar sign.
100
101Misc
102~~~~
103
104
105* link:https://code.google.com/p/gerrit/issues/detail?id=2564[Issue 2564],
106link:https://code.google.com/p/gerrit/issues/detail?id=2571[Issue 2571]:
107Emit ref-updated event when editing project access via Web UI.
108
109* link:https://code.google.com/p/gerrit/issues/detail?id=2557[Issue 2557]:
110By default don't allow admins to create new branches by push.
111+
112When pushing changes it is easy to make a typo in the refspec and in this case
113new branches should not be created. If administrators want to create branches
114by push they should explicitly assign themselves the needed access rights.
115
116* Do not refresh project list if filter did not change.
117+
118The project list was being refreshed on every key event even if the
119filter did not change, e.g. moving the cursor inside the text entry was
120causing the list to update unnecessarily.
121
122* Fix mail thread getting stuck when waiting for response from SMTP server.
123+
124It is now possible to configure the default thread pool size, the size of
125the thread pool for sending emails, and the SMTP server connection timeout.
126
127* link:https://code.google.com/p/gerrit/issues/detail?id=2215[Issue 2215]:
128Paginate the project list screen.
129+
130The project list screen was taking a long time to render over a large
131amount of projects (1,000+) and with even larger number of projects
132(3,000+), it could make the browser unresponsive.
133+
134The project list screen now uses pagination to resolve this issue. The
135number of projects displayed is determined by the 'Maximum Page Size'
136user preference.
137+
138Option 'S' is added to the projects REST API to support query offset.
139
140* link:https://code.google.com/p/gerrit/issues/detail?id=2599[Issue 2599]:
141Always auto confirm adding reviewers in `set-reviewers` SSH command.
142+
143If a group contains more than 'addreviewer.maxWithoutConfirmation'
144members, adding it as reviewer to a change requires a confirmation. A
145user should only be asked for the confirmation when reviewers are
146added from the Web UI but not when the `set-reviewers` SSH command is
147used.
148
149* Set uploader to current user in `patchset-created` event upon cherry-picking.
150+
151When using the Web UI (both old and new change screens) to cherry-pick a
152change to a branch that already has this change (e.g. cherry-picking
153on the same branch to get rid of dependencies), the corresponding
154`patchset-created` event had its `patchSet.uploader` set to the change's
155owner instead of the current user. It is now set to the current user,
156so stream-events consumers can properly detect who uploaded the
157rebased patch set.
158
159Documentation
160~~~~~~~~~~~~~
161
162
163* link:https://code.google.com/p/gerrit/issues/detail?id=1273[Issue 1273]:
164Update the MySQL documentation concerning character sets.
165+
166The setup documentation is updated to mention that there is no need to use
167latin1 encoding if you are using an engine other than MyISAM.
168
169* Use consistent grammatical tense in ssh command descriptions.
170
171* Add more detail about `refs/drafts` in
172link:https://gerrit-documentation.storage.googleapis.com/Documentation/2.8.4/access-control.html[
173access control documentation].