| Shawn O. Pearce | 55e9025 | 2011-05-31 10:30:18 -0700 | [diff] [blame] | 1 | Release notes for Gerrit 2.2.0 |
| 2 | ============================== |
| 3 | |
| 4 | Gerrit 2.2.0 is now available: |
| 5 | |
| 6 | link:http://code.google.com/p/gerrit/downloads/detail?name=gerrit-2.2.0.war[http://code.google.com/p/gerrit/downloads/detail?name=gerrit-2.2.0.war] |
| 7 | |
| 8 | Schema Change |
| 9 | ------------- |
| 10 | *WARNING:* Upgrading to 2.2.0 requires the server be first upgraded |
| 11 | to 2.1.7, and then to 2.2.0. |
| 12 | |
| 13 | *WARNING:* This release contains schema changes. To upgrade: |
| 14 | ---- |
| 15 | java -jar gerrit.war init -d site_path |
| 16 | ---- |
| 17 | |
| 18 | *WARNING:* The "projects" and "ref_rights" tables are no longer |
| 19 | stored in the SQL database. The tables have been moved to Git |
| 20 | storage, inside of the `refs/meta/config` branch of each managed |
| 21 | Git repository. The init based upgrade tool will automatically |
| 22 | export the current table contents and create the Git data. |
| 23 | |
| 24 | New Features |
| 25 | ------------ |
| 26 | |
| 27 | Project Administration |
| 28 | ~~~~~~~~~~~~~~~~~~~~~~ |
| 29 | * issue 436 List projects by scanning the managed Git directory |
| 30 | + |
| 31 | Instead of generating the list of projects from SQL database, the |
| 32 | project list is obtained by recursively scanning the Git directory. |
| 33 | Adding new projects is now simply a matter of creating the Git |
| 34 | repository under the directory and flushing the "projects" cache |
| 35 | to force the server to rescan the directory. Administrators may |
| 36 | also continue to use `gerrit create-project`. |
| 37 | |
| 38 | * Move "projects" table into Git |
| 39 | + |
| 40 | The projects table columns are now stored in the `project.config` |
| 41 | file of the `refs/meta/config` branch of each managed Git repository. |
| 42 | |
| 43 | * Move "ref_rights" table into Git |
| 44 | + |
| 45 | The "ref_rights" table is now stored in the "access" sections of |
| 46 | the `project.config` file on the `refs/meta/config` branch of each |
| 47 | managed Git repository. This brings version control auditing to the |
| 48 | access data of each project. |
| 49 | |
| 50 | * New project Access screen to edit access controls |
| 51 | + |
| 52 | The Access panel of the project administration has been rewritten |
| 53 | with a new UI that reflects the new Git based storage format. |
| 54 | |
| 55 | Bug Fixes |
| 56 | --------- |
| 57 | |
| 58 | Project Administration |
| 59 | ~~~~~~~~~~~~~~~~~~~~~~ |
| 60 | * Avoid unnecessary updates to $GIT_DIR/description |
| 61 | + |
| 62 | Gerrit always tried to rewrite the gitweb "description" file when the |
| 63 | project was modified. This lead to unnecessary changes in the local |
| 64 | filesystem, leading to more data to rsync to backups than necessary. |
| 65 | Fixed to only update the file if the content changes. |
