opendev/gerrit
Code Issues Proposed changes

Document library upgrade process

Browse Source 
Change-Id: I8c3baff128beb4c47c8bd95c075917648bcc6ac1
This commit is contained in:
Patrick Hiesel 2017-04-18 09:27:15 +02:00
parent 38161a85cc
commit b1bf7594df
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/dev-contributing.txt
View File

@ -344,6 +344,18 @@ category in the issue tracker and try to assign easy hack projects to it. If in
doubt, do not hesitate to ask on the developer
link:https://groups.google.com/forum/#!forum/repo-discuss[mailing list].
=== Upgrading Libraries
Gerrit's library dependencies should only be upgraded if the new version contains
something we need in Gerrit. This includes new features, API changes as well as bug
or security fixes.
An exception to this rule is that right after a new Gerrit release was branched
off, all libraries should be upgraded to the latest version to prevent Gerrit
from falling behind. Doing those upgrades should conclude at the latest two
months after the branch was cut. This should happen on the master branch to ensure
that they are vetted long enough before they go into a release and we can be sure
that the update doesn't introduce a regression.
GERRIT
------
Part of link:index.html[Gerrit Code Review]