summaryrefslogtreecommitdiff
path: root/HACKING.txt
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2018-05-19 06:42:10 -0700
committerSteve Piercy <web@stevepiercy.com>2018-05-19 06:42:10 -0700
commit2cbea29fae5adf311d46b6a1f1dcf8d71a64e5bd (patch)
tree531c6792d59ad2448d75edc970a764729f299214 /HACKING.txt
parent85900228894814105aa882e1e71f1e4e69090a9e (diff)
downloadpyramid-2cbea29fae5adf311d46b6a1f1dcf8d71a64e5bd.tar.gz
pyramid-2cbea29fae5adf311d46b6a1f1dcf8d71a64e5bd.tar.bz2
pyramid-2cbea29fae5adf311d46b6a1f1dcf8d71a64e5bd.zip
use correct file extension for CHANGES
Diffstat (limited to 'HACKING.txt')
-rw-r--r--HACKING.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/HACKING.txt b/HACKING.txt
index 20cff7cac..8ec44605c 100644
--- a/HACKING.txt
+++ b/HACKING.txt
@@ -242,7 +242,7 @@ or adds the feature. To build and review docs, use the following steps.
Change Log
----------
-- Feature additions and bugfixes must be added to the ``CHANGES.txt``
+- Feature additions and bugfixes must be added to the ``CHANGES.rst``
file in the prevailing style. Changelog entries should be long and
descriptive, not cryptic. Other developers should be able to know
what your changelog entry means.