David Pursehouse | 7fe39b9 | 2014-10-22 18:32:33 +0900 | [diff] [blame] | 1 | Release notes for Gerrit 2.9.2 |
| 2 | ============================== |
| 3 | |
| 4 | Download: |
| 5 | link:https://gerrit-releases.storage.googleapis.com/gerrit-2.9.2.war[ |
| 6 | https://gerrit-releases.storage.googleapis.com/gerrit-2.9.2.war] |
| 7 | |
| 8 | Important Notes |
| 9 | --------------- |
| 10 | |
| 11 | *WARNING:* There are no schema changes from |
| 12 | link:ReleaseNotes-2.9.1.html[2.9.1], but when upgrading from an existing site |
David Pursehouse | 58ac7a9 | 2014-11-28 17:55:48 +0900 | [diff] [blame] | 13 | that was initialized with Gerrit version 2.6 or later the primary key column |
David Pursehouse | 7fe39b9 | 2014-10-22 18:32:33 +0900 | [diff] [blame] | 14 | order will be updated for some tables. It is therefore important to upgrade the |
| 15 | site with the `init` program, rather than only copying the .war file over the |
| 16 | existing one. |
| 17 | |
| 18 | It is recommended to run the `init` program in interactive mode. Warnings will |
| 19 | be suppressed in batch mode. |
| 20 | |
| 21 | ---- |
| 22 | java -jar gerrit.war init -d site_path |
| 23 | ---- |
| 24 | |
| 25 | Bug Fixes |
| 26 | --------- |
| 27 | |
| 28 | ssh |
| 29 | ~~~ |
| 30 | |
| 31 | * Update SSHD to 0.13.0. |
| 32 | + |
| 33 | This fixes link:https://issues.apache.org/jira/browse/SSHD-348[SSHD-348] which |
| 34 | was causing ssh threads allocated to stream-events clients to get stuck. |
| 35 | + |
| 36 | Also update SSHD Mina to 2.0.8 and Bouncycastle to 1.51. |
| 37 | |
| 38 | Database |
| 39 | ~~~~~~~~ |
| 40 | |
| 41 | * Update gwtorm to 1.14. |
| 42 | + |
| 43 | The primary key column order for compound keys was wrong for some Gerrit |
| 44 | database tables. This caused poor performance for those SQL queries which rely |
| 45 | on using a prefix of the primary key column sequence in their WHERE conditions. |
| 46 | + |
| 47 | This version of gwtorm fixes the issue for new sites. For existing sites that |
David Pursehouse | 58ac7a9 | 2014-11-28 17:55:48 +0900 | [diff] [blame] | 48 | were initialized with Gerrit version 2.6 or later, the primary key column |
| 49 | order will be fixed during initialization when upgrading to 2.9.2. |
David Pursehouse | 7fe39b9 | 2014-10-22 18:32:33 +0900 | [diff] [blame] | 50 | |
| 51 | Secondary Index |
| 52 | ~~~~~~~~~~~~~~~ |
| 53 | |
| 54 | * Fix "400 cannot create query for index" error in "Conflicts With" list. |
| 55 | + |
| 56 | The new |
| 57 | link:https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.2/config-gerrit.html#index.defaultMaxClauseCount[ |
| 58 | index.defaultMaxClauseCount] setting allows to increase the BooleanQuery limit |
| 59 | for the Lucene index. |
| 60 | + |
| 61 | Raising the limit avoids failing a query with `BooleanQuery.TooManyClauses`, |
| 62 | preventing users from seeing a "400 cannot create query for index" error |
| 63 | in the "Conflicts With" section of the change screen. |
| 64 | |
| 65 | * link:https://code.google.com/p/gerrit/issues/detail?id=2996[Issue 2996]: |
| 66 | Delete a change from the index if it is not in the database. |
| 67 | + |
| 68 | If for some reason the secondary index is out of date, i.e. a change was deleted |
| 69 | from the database but wasn't deleted from the secondary index, it was impossible |
| 70 | to re-index (remove) that change. |
| 71 | + |
| 72 | Automatically remove the change from the secondary index if it doesn't exist in |
| 73 | the database. If a user clicks on search result from a stale change, they will |
| 74 | get a 404 page and the change will be removed from the index. |
| 75 | |
| 76 | Change Screen |
| 77 | ~~~~~~~~~~~~~ |
| 78 | |
| 79 | * link:https://code.google.com/p/gerrit/issues/detail?id=2964[Issue 2964]: |
| 80 | Fix comment box font colors of dark CodeMirror themes. |
| 81 | + |
| 82 | When using a dark-colored theme, for example "Twilight", the comments were |
| 83 | shown in a light color on a light background making them unreadable. |
| 84 | |
| 85 | * link:https://code.google.com/p/gerrit/issues/detail?id=2918[Issue 2918]: |
| 86 | Fix placement of margin column in side-by-side diff. |
| 87 | + |
| 88 | The margin was placed approximately 10% too far to the right. |
| 89 | |
| 90 | * link:https://code.google.com/p/gerrit/issues/detail?id=2970[Issue 2970]: |
| 91 | Fix display of accented characters in side-by-side diff. |
| 92 | + |
| 93 | On some browsers, accented characters were not displayed correctly |
| 94 | because the line was not high enough. |
| 95 | |
| 96 | * link:https://code.google.com/p/gerrit/issues/detail?id=2960[Issue 2960]: |
| 97 | Show filename in side-by-side diff screen. |
| 98 | + |
| 99 | In the old side-by-side diff screen, the name of the file being diffed was shown |
| 100 | in the window title. This feature was missed in the new side-by-side diff screen. |
| 101 | |
| 102 | * Remove 'send email' checkbox from reply box on change screen. |
| 103 | |
| 104 | Plugins |
| 105 | ~~~~~~~ |
| 106 | |
| 107 | * link:https://code.google.com/p/gerrit/issues/detail?id=543[Issue 543] |
| 108 | Replication plugin: Prevent creating repos on extra servers. |
| 109 | + |
| 110 | If using a group to replicate only certain repositories, it was possible |
| 111 | to be in a state where the authGroup is used on some servers but not |
| 112 | others. If this happened, Gerrit would create the repository on all |
| 113 | servers, even if the authGroup would prevent replicating code to it. |
| 114 | By ensuring the authGroup can see the project first, the repository is |
| 115 | not created if it's not needed. |
| 116 | |
| 117 | Security |
| 118 | ~~~~~~~~ |
| 119 | |
| 120 | * Do not throw away bytes from the CNSPRG when generating HTTP passwords. |
| 121 | + |
| 122 | The implementation generated LEN bytes of cryptography-safe random data and |
| 123 | applied base64 encoding on top of that. The base64 transformation, however, |
| 124 | inflated the size of the data by 33%, and this meant that only 9 bytes of |
| 125 | randomness were actually used. |
| 126 | |
| 127 | * Increase the size of HTTP passwords. |
| 128 | + |
| 129 | The length of generated HTTP passwords is increased from 12 to 42 characters. |
| 130 | |
| 131 | * Consider rule action while constructing local owners list |
| 132 | + |
| 133 | Previously rule action was not considered during computation of the local |
| 134 | owners list. This meant that members of a group that was given OWNER permission |
| 135 | with BLOCK or DENY action were considered as project owners. |
| 136 | |
| 137 | |
| 138 | Miscellaneous Fixes |
| 139 | ~~~~~~~~~~~~~~~~~~~ |
| 140 | |
| 141 | * link:https://code.google.com/p/gerrit/issues/detail?id=2911[Issue 2911]: |
| 142 | Fix Null Pointer Exception after a MergeValidationListener throws |
| 143 | MergeValidationException. |
| 144 | |
| 145 | * link:https://code.google.com/p/gerrit/issues/detail?id=2989[Issue 2989]: |
| 146 | Fix incorrect submodule subscriptions. |
| 147 | + |
| 148 | The gitlinks update failed after deleting a branch in a super project which had |
| 149 | other branches subscribed to the same submodule branch. |
| 150 | |
| 151 | * Fix infinite loop when checking group membership. |
| 152 | |
| 153 | * Fix quoted-printable encoding of e-mail addresses. |
| 154 | + |
| 155 | The "(Code Review)" part of the e-mail sender name was truncated when the |
| 156 | author's name was not pure ASCII. |