Added directions for placement of release notes for contributed features collab/berick/release-notes-next-hacking
authorBill Erickson <berick@esilibrary.com>
Wed, 23 May 2012 20:54:30 +0000 (16:54 -0400)
committerBill Erickson <berick@esilibrary.com>
Wed, 23 May 2012 20:54:30 +0000 (16:54 -0400)
Signed-off-by: Bill Erickson <berick@esilibrary.com>
HACKING

diff --git a/HACKING b/HACKING
index f270c58..79736b6 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -8,6 +8,11 @@ Contributing
 A
 http://evergreen-ils.org/dokuwiki/doku.php?id=contributing[tutorial for contributing to Evergreen is on the Evergreen Wiki].
 
+Feature Release Notes
+~~~~~~~~~~~~~~~~~~~~~
+
+New features should be accompanied by a file in the repository under the docs/RELEASE_NOTES_NEXT/ directory. The file should be in asciidoc format and contain enough description to enable the documentation team to write something coherent about the new functionality. As much as possible, the name of the file should match the feature. No numbering, etc. is required.
+
 Git
 ---