[pkgsrc/trunk]: pkgsrc/doc/guide/files There are some rules for adding a chan...

[rillig <rillig%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/84a5aaaa0b6a
branches:  trunk
changeset: 509087:84a5aaaa0b6a
user:      rillig <rillig%pkgsrc.org@localhost>
date:      Thu Mar 02 23:08:40 2006 +0000

description:
There are some rules for adding a change to doc/CHANGES when the
PKGREVISION is bumped. If none of the rules applies, the behavior is
developer-dependent.

diffstat:

 doc/guide/files/submit.xml |  9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)

diffs (23 lines):

diff -r 6477b3faa347 -r 84a5aaaa0b6a doc/guide/files/submit.xml
--- a/doc/guide/files/submit.xml        Thu Mar 02 23:01:12 2006 +0000
+++ b/doc/guide/files/submit.xml        Thu Mar 02 23:08:40 2006 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: submit.xml,v 1.9 2006/02/12 14:44:59 rillig Exp $ -->
+<!-- $NetBSD: submit.xml,v 1.10 2006/03/02 23:08:40 rillig Exp $ -->
 
 <chapter id="submit"> <?dbhtml filename="submit.html"?>
 <title>Submitting and Committing</title>
@@ -63,6 +63,13 @@
   for the package you updated or removed, in case it was mentioned
   there.</para>
 
+       <para>When the <varname>PKGREVISION</varname> of a package is
+       bumped, the change should appear in
+       <filename>pkgsrc/doc/CHANGES</filename> if it is security
+       related or otherwise relevant. Mass bumps that result from a
+       dependency being updated should not be mentioned. In all other
+       cases it's the developer's decision.</para>
+
 <para>There is a make target that helps in creating proper
   <filename>CHANGES</filename> entries:  <command>make
   changes-entry</command>. It uses the optional <varname>CTYPE</varname>