| commit | 04e4cd95788f41e8a5ca86c99f63aad6b3da603c | [log] [tgz] |
|---|---|---|
| author | Marco Miller <marco.miller@ericsson.com> | Wed Oct 14 17:48:29 2020 -0400 |
| committer | Marco Miller <marco.miller@ericsson.com> | Fri Oct 16 16:10:53 2020 -0400 |
| tree | b0d293117d9d1d8c7db3f8bc9d56b2828b14b62b | |
| parent | 894b89d0fa0c693781171a7d7aefb2261f2c93af [diff] |
Split release_noter generated notes into more component sections Order each such component(s) section by Components declaration order. This allows for a specific ordering of the sections on the notes page. That order starts with submodule plugins, followed by other Components. Ordering is based on going from less crowded sections to the most busy one, for other or non-classified (default) core changes. User-facing changes are to be listed right after the core plugin ones. The latter are listed first for script implementation purposes. The editor can move those around at will while finalizing the real notes. The thing is, the many changes that are deeper in core are to be listed after, to not clutter the top-most sections. Some components are listed before others because they would otherwise be classified more generically. E.g., the jgit and elastic sections get listed before the other dependencies one, as being more outstanding components compared to other libraries. Just like more excluded subjects can be eventually added, more components or sections (or sentinels) can be easily added later on. Soften the generated section titles by using lowercase more in them. Feature: Issue 13519 Change-Id: I70e1cec934d414afd1e1372a197e4ee3ff1855c4
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 8 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8
To run a Ubuntu 20.04 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.