summaryrefslogtreecommitdiff
path: root/CONTRIBUTE
diff options
context:
space:
mode:
authorAndrew Hyatt <ahyatt@gmail.com>2016-01-01 15:07:53 -0500
committerAndrew Hyatt <ahyatt@gmail.com>2016-01-01 15:07:53 -0500
commit222796697a6d1cae1d965df80fc42613f5fb1f89 (patch)
tree280902cf86bbbf61224db6dee31e9f56e984aadb /CONTRIBUTE
parentee0117c4a859f7d8c37661c60aa4736add4dd53f (diff)
downloademacs-222796697a6d1cae1d965df80fc42613f5fb1f89.tar.gz
Add notes on bug triage procedure
* CONTRIBUTE: In section on the issue tracker, point to new triage file. * admin/notes/triage: New file explaining triage procedure.
Diffstat (limited to 'CONTRIBUTE')
-rw-r--r--CONTRIBUTE11
1 files changed, 11 insertions, 0 deletions
diff --git a/CONTRIBUTE b/CONTRIBUTE
index b385d68c985..0c0ef207ff3 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -222,6 +222,17 @@ 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/triage.
+
** Document your changes.
Any change that matters to end-users should have an entry in etc/NEWS.