diff options
| author | Eli Zaretskii <eliz@gnu.org> | 2018-04-28 15:03:17 +0300 |
|---|---|---|
| committer | Eli Zaretskii <eliz@gnu.org> | 2018-04-28 15:03:17 +0300 |
| commit | 4403f89056d36d23404b3272f405b65bea312bf2 (patch) | |
| tree | a299ebd4c6208182a13606a19c56fe9c709add08 /admin/release-process | |
| parent | 40b3317046fc527e3e3d266a8a51f9cf057aa6be (diff) | |
| download | emacs-4403f89056d36d23404b3272f405b65bea312bf2.tar.gz | |
Update the Emacs FAQ
* doc/misc/efaq.texi (Latest version of Emacs): Update versions.
(New in Emacs 26): New node.
* admin/release-process: Mention the FAQ update as part of the
release.
Diffstat (limited to 'admin/release-process')
| -rw-r--r-- | admin/release-process | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/admin/release-process b/admin/release-process index 3bb72b9735c..71ada82356c 100644 --- a/admin/release-process +++ b/admin/release-process @@ -99,6 +99,10 @@ significant changes and new features in the upcoming release, then describe the "benefits" from losing those features. Be funny, use humor. The text written for the previous releases can serve as an example. +The Emacs FAQ (doc/misc/efaq.texi) also has a "What's new" section; +for major releases a new section should be added listing the +significant changes. + Check cross-references between the manuals (e.g. from emacs to elisp) are correct. You can use something like the following in the info directory in the Emacs build tree: |