X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/503e752c4a4ec4dc05c112ae82753b85594c99be..HEAD:/CONTRIBUTE

diff --git a/CONTRIBUTE b/CONTRIBUTE
index a70682f29a..9d5d775a5e 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -233,6 +233,17 @@ above, are recorded by the tracker with the corresponding bugs/issues.
 GNU ELPA has a 'debbugs' package that allows accessing the tracker
 database from Emacs.
 
+Bugs needs regular attention.  A large backlog of bugs is
+disheartening to the developers, and a culture of ignoring bugs is
+harmful to users, who expect software that works.  Bugs have to be
+regularly looked at and acted upon.  Not all bugs are critical, but at
+the least, each bug needs to be regularly re-reviewed to make sure it
+is still reproducible.
+
+The process of going through old or new bugs and acting on them is
+called bug triage.  This process is described in the file
+admin/notes/bug-triage.
+
 ** Documenting your changes
 
 Any change that matters to end-users should have an entry in etc/NEWS.
@@ -264,10 +275,9 @@ If your test lasts longer than some few seconds, mark it in its
 'ert-deftest' definition with ":tags '(:expensive-test)".
 
 To run tests on the entire Emacs tree, run "make check" from the
-top-level directory.  Most tests are in the directory
-"test/automated".  From the "test/automated" directory, run "make
-<filename>" to run the tests for <filename>.el(c).  See "test/README"
-for more information.
+top-level directory.  Most tests are in the directory "test/".  From
+the "test/" directory, run "make <filename>" to run the tests for
+<filename>.el(c).  See "test/README" for more information.
 
 ** Understanding Emacs internals