Author: jrdioko-guest Date: 2011-07-25 03:39:54 +0000 (Mon, 25 Jul 2011) New Revision: 16977 Modified: doc/narrative_introduction Log: Add details to "Checking in your changes" section Mention that normally changes can be committed directly and are peer reviewed through the mailing list, but changes to the tracker should be emailed and discussed before committing. Modified: doc/narrative_introduction ==================================================================--- doc/narrative_introduction 2011-07-24 17:54:31 UTC (rev 16976) +++ doc/narrative_introduction 2011-07-25 03:39:54 UTC (rev 16977) @@ -441,9 +441,17 @@ There is a script running, which automatically commits them to DSA/list. In some cases it needs manual fixups. -Checking your changes ---------------------- +Checking in your changes +------------------------ +After thoroughly researching each issue (as described above) and editing +the relevant files, commit your changes. Peer review is done via the +mailing list and IRC notifications (see "Automatic Issue Updates" above). +However, changes to the tracker website itself (e.g. the files in bin/) +should be vetted and approved before being committed. The preferred way +to do this is to send a patch to the +debian-security-tracker at lists.debian.org mailing list. + Commits are checked for syntax errors before they are actually committed, and you''ll receive an error and your commit is aborted if it is in error. To check your changes yourself beforehand, use "make check-syntax" from