diff options
| author | Stefano Lattarini <stefano.lattarini@gmail.com> | 2012-12-19 13:06:10 +0100 |
|---|---|---|
| committer | Stefano Lattarini <stefano.lattarini@gmail.com> | 2012-12-19 13:06:10 +0100 |
| commit | fe45ffc9ac54db568c65071d9602d639cfbeadb6 (patch) | |
| tree | e946cf9374b058c0cdb02f002f4d97b6a0b3ee5e /HACKING | |
| parent | b89735306369694f5a88dfa9ffb54c81acf245c9 (diff) | |
| parent | 929c20cc15c3188dd3bf7557ab3dad62c6db2178 (diff) | |
| download | automake-fe45ffc9ac54db568c65071d9602d639cfbeadb6.tar.gz | |
Merge branch 'master' into ng/master
* master:
maint: typofixes in makefile comments
maint: remove extra verbosity from a maintainer rule
NEWS: fix grammaro
maint: version bump after beta release
release: beta release 1.12b (will become 1.13)
cosmetics: comments fixlets in our Makefile
cosmetics: consistency changes in some make recipes
tests: avoid a spurious failure on NetBSD
tests: re-enable some checks disabled by mistake ...
tests: avoid a "grep -E" portability issue
tests: avoid a spurious failure due to a Clang bug
NEWS: start preparing for the 1.13 release
tests: typofix in the shebang line of 't/py-compile-destdir.sh'
HACKING: release process: fixlets about the announcement
maint: post-release minor version bump
release: stable release 1.12.5
tests: avoid errors due to underquoted third-party macros
maintcheck: also consider contrib tests for syntax checks
cosmetics: whitespace fixlets in syntax-checks.mk
Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 24 |
1 files changed, 14 insertions, 10 deletions
@@ -275,23 +275,27 @@ - Check for link errors, fix them, recheck until convergence: <http://validator.w3.org/checklink> +* Create an announcement message with "make announcement". Edit the + generated 'announcement' file appropriately, in particularly filling + in by hand any "TODO" left in there. + * Update version number in configure.ac to next alpha number. Re-run ./bootstrap.sh and commit. * Don't forget to "git push" your changes so they appear in the public git tree. -* Create an announcement message with "make announcement". Edit the - generated 'announcement' file appropriately, in particularly filling - in by hand any "TODO" left in there. - -* Send the announcement at least to <autotools-announce@gnu.org> and - <automake@gnu.org>. If the release is a stable one, the announcement - must also go to <info-gnu@gnu.org>; if it is an alpha or beta release, - announcement should be sent also to <platform-testers@gnu.org>, to - maximize the possibility of early testing on exotic or proprietary - systems. Finally, copy the announcement into the NEWS feed at +* Send the announcement generated in the earlier steps at least to + <autotools-announce@gnu.org> and <automake@gnu.org>. If the release + is a stable one, the announcement must also go to <info-gnu@gnu.org>; + if it is an alpha or beta release, announcement should be sent also + to <platform-testers@gnu.org>, to maximize the possibility of early + testing on exotic or proprietary systems. Finally, copy an abridged + version of the announcement into the NEWS feed at: <https://savannah.gnu.org/projects/automake>. + Be sure to link a version to the complete announcement (from + the version you sent to the automake list, as get archived on + <http://lists.gnu.org/archive/html/automake/>). ----- |