appropriate paperwork.
Second, be sure to add their name and email address to THANKS
-* If a change fixes a test, mention the test in the ChangeLog entry.
+* If a change fixes a test, mention the test in the commit message.
If a change fixes a bug registered in the Automake debbugs tracker,
- mention the bug number in the ChangeLog entry.
+ mention the bug number in the commit message.
-* If somebody reports a new bug, mention his name in the ChangeLog entry
+* If somebody reports a new bug, mention his name in the commit message
and in the test case you write. Put him into THANKS.
* When documenting a non-trivial idiom or example in the manual, be
release. For next, and for feature branches, the announcement for the
branch should document rewinding policy.
-* In order for rebasing and merging of ChangeLog entries to work seamlessly,
- install and configure git-merge-changelog, currently available as gnulib
- module.
-
================================================================
= Test suite
The repository will always have its own "odd" number so we can easily
distinguish net and repo versions.)
-* Update ChangeLog.
-
* Run this:
./bootstrap && ./configure && make && make check && make distcheck
* Run `make git-release'.
This will run "make dist" to create the tarballs, commit the last
- NEWS/configure.ac/ChangeLog changes, tag the repository, sign
- the tarballs, and upload them.
+ changes to NEWS, configure.ac and m4/amversion.m4, tag the repository,
+ sign the tarballs, and upload them.
Use `make GNUPLOADFLAGS="--user key" git-release' to sign with
a non-default key.
-----
-Copyright (C) 2003, 2007, 2008, 2010, 2011 Free Software Foundation,
-Inc.
+Copyright (C) 2003, 2007, 2008, 2010, 2011, 2012 Free Software
+Foundation, Inc.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by