doc: Add Gerrit to the Developer resources section
Change-Id: Icbf2050967cea06b05a09574a6a91ce1407a489f Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com> Reviewed-on: http://openocd.zylin.com/1885 Tested-by: jenkins Reviewed-by: Paul Fertser <fercerpav@gmail.com> Reviewed-by: Xiaofan <xiaofanc@gmail.com> Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>__archive__
parent
6c1437a0a4
commit
957c324204
|
@ -262,6 +262,25 @@ This document is a work-in-progress, but contributions would be welcome
|
||||||
to fill in the gaps. All of the source files are provided in-tree,
|
to fill in the gaps. All of the source files are provided in-tree,
|
||||||
listed in the Doxyfile configuration at the top of the source tree.
|
listed in the Doxyfile configuration at the top of the source tree.
|
||||||
|
|
||||||
|
@section Gerrit Review System
|
||||||
|
|
||||||
|
All changes in the OpenOCD Git repository go through the web-based Gerrit
|
||||||
|
Code Review System:
|
||||||
|
|
||||||
|
@uref{http://openocd.zylin.com/}
|
||||||
|
|
||||||
|
After a one-time registration and repository setup, anyone can push commits
|
||||||
|
from their local Git repository directly into Gerrit.
|
||||||
|
All users and developers are encouraged to review, test, discuss and vote
|
||||||
|
for changes in Gerrit. The feedback provides the basis for a maintainer to
|
||||||
|
eventually submit the change to the main Git repository.
|
||||||
|
|
||||||
|
The @file{HACKING} file, also available as the Patch Guide in the Doxygen
|
||||||
|
Developer Manual, contains basic information about how to connect a
|
||||||
|
repository to Gerrit, prepare and push patches. Patch authors are expected to
|
||||||
|
maintain their changes while they're in Gerrit, respond to feedback and if
|
||||||
|
necessary rework and push improved versions of the change.
|
||||||
|
|
||||||
@section OpenOCD Developer Mailing List
|
@section OpenOCD Developer Mailing List
|
||||||
|
|
||||||
The OpenOCD Developer Mailing List provides the primary means of
|
The OpenOCD Developer Mailing List provides the primary means of
|
||||||
|
@ -269,10 +288,6 @@ communication between developers:
|
||||||
|
|
||||||
@uref{https://lists.sourceforge.net/mailman/listinfo/openocd-devel}
|
@uref{https://lists.sourceforge.net/mailman/listinfo/openocd-devel}
|
||||||
|
|
||||||
Discuss and submit patches to this list.
|
|
||||||
The @file{HACKING} file contains basic information about how
|
|
||||||
to prepare patches.
|
|
||||||
|
|
||||||
@section OpenOCD Bug Database
|
@section OpenOCD Bug Database
|
||||||
|
|
||||||
During the 0.4.x release cycle the OpenOCD project team began
|
During the 0.4.x release cycle the OpenOCD project team began
|
||||||
|
|
Loading…
Reference in New Issue