aboutsummaryrefslogtreecommitdiffstats
path: root/admin
diff options
context:
space:
mode:
authorEli Zaretskii2018-04-28 15:03:17 +0300
committerEli Zaretskii2018-04-28 15:03:17 +0300
commit4403f89056d36d23404b3272f405b65bea312bf2 (patch)
treea299ebd4c6208182a13606a19c56fe9c709add08 /admin
parent40b3317046fc527e3e3d266a8a51f9cf057aa6be (diff)
downloademacs-4403f89056d36d23404b3272f405b65bea312bf2.tar.gz
emacs-4403f89056d36d23404b3272f405b65bea312bf2.zip
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')
-rw-r--r--admin/release-process4
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
99describe the "benefits" from losing those features. Be funny, use 99describe the "benefits" from losing those features. Be funny, use
100humor. The text written for the previous releases can serve as an example. 100humor. The text written for the previous releases can serve as an example.
101 101
102The Emacs FAQ (doc/misc/efaq.texi) also has a "What's new" section;
103for major releases a new section should be added listing the
104significant changes.
105
102Check cross-references between the manuals (e.g. from emacs to elisp) 106Check cross-references between the manuals (e.g. from emacs to elisp)
103are correct. You can use something like the following in the info 107are correct. You can use something like the following in the info
104directory in the Emacs build tree: 108directory in the Emacs build tree: