Document ChangeLog policy change

ChangeLog

@@ -1,5 +1,15 @@
 Older entries can be found in ChangeLog-1.0.25.
 
+For the latest changes please refer to the output of `git log` or the
+on-line log at:
+
+      https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=sane/sane-backends.git;a=log
+
+Note to developers:
+      For 1.0.26 and beyond we will generate the ChangeLog from the git
+      commit messages at release time.  Instead of documenting your work
+      here, just document it in your commit messages.
+
 2015-10-14 Rolf Bensch <rolf at bensch hyphen online dot de>
     * backend/pixma_mp730.c, doc/descriptions/pixma.desc, doc/sane-pixma.man:
       New scanners Canon PIXUS MP5/SmartBase MPC190/imageCLASS MPC190 and

doc/backend-writing.txt

@@ -80,11 +80,12 @@ sane-backends/
     configure.in depcomp install-sh ltmain.sh Makefile.am Makefile.in missing 
     mkinstalldirs: Part of the build system as explained above.
   * ChangeLog:
-    The ChangeLog contains all the changes made since the last stable release. 
-    If anything is changed in git, it must be also mentioned in ChangeLog. 
-    It's not enough to write just a git commit message, as users won't have 
-    access to these messages. For more details on the format, see the SANE 
-    git page on the website.
+    The ChangeLog contains all the changes made since the last stable release.
+    If anything is changed in git, write a decent commit message documenting
+    your work.  This commit message will be included as is in the ChangeLog
+    file for the next stable release.  Users of development code should refer
+    to the `git log` output or the on-line log.
+    For more details on the format, see the SANE git page on the website.
   * ChangeLog-1.0.0, ChangeLog-1.0.1 (...):
     These files contain the ChangeLogs of older releases. Once a new release has
     been made, the current ChangeLog renamed to ChangeLog-1.something.something