From 3b908c3cefcf6d1258a9acd69549b2daa2d28a4d Mon Sep 17 00:00:00 2001 From: Johnathan Ritzi Date: Mon, 25 Jul 2011 03:39:54 +0000 Subject: 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. git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@16977 e39458fd-73e7-0310-bf30-c45bca0a0e42 --- doc/narrative_introduction | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) (limited to 'doc/narrative_introduction') diff --git a/doc/narrative_introduction b/doc/narrative_introduction index 4c831e3b3a..76a223e500 100644 --- a/doc/narrative_introduction +++ b/doc/narrative_introduction @@ -441,8 +441,16 @@ DSA entry once the official DSA is published on debian-security-announce. 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@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. -- cgit v1.2.3