1 Tasks needed before the next release.
3 * TO BE DONE SHORTLY BEFORE RELEASE
6 Check cross-references between the manuals (eg from emacs to elisp)
7 are correct. You can use something like the following in the info
8 directory in the Emacs build tree:
10 emacs -Q --eval "(setq Info-default-directory-list '(\".\"))" \
11 -f info-xref-check-all
13 make emacs.dvi, elisp.dvi, and deal with any errors (undefined
14 references etc) in the output. Break any overfull lines.
15 Underfull hboxes are not serious, but it can be nice to get rid of
16 them if a simple rephrasing or rearrangement will work.
18 Update the master menu and detailed menu (eg the antinews version).
19 The command texinfo-multiple-files-update can do this, but you
20 probably want to apply the results selectively (eg the current master
21 menu has better line-breaks than the automatic version). It includes
22 the menu-entry name (if there is one) as well as the node name - using
23 only the latter looks better. Also, it doesn't seem to handle nested
24 includes, so will miss edebug.texi etc.
26 Check for widow and orphan lines in the printed manual; make sure all
27 the pages really look ok in the manual as formatted. Orphans/widows
28 are cases where the first/last line of a paragraph is on its own at
29 the end/start of a page, or where the last word in a paragraph is on
30 its own at the start of a line. It looks better if you reword/respace
31 things to avoid these. (AFAIK, there is no way to find these except
32 paging through the whole manual.) This should be the very last thing
33 you do, since any change can alter the layout.
35 ** Regenerate the pdf versions of the reference cards in etc/refcards/.
37 ** Ask maintainers of refcard translations to update them.
41 LANG Translator Status
50 ** Remove temporary +++/--- lines in NEWS.
52 ** Try to reorder NEWS: most important things first, related items together.
54 ** Consider bumping customize-changed-options-previous-release.
58 ** Does deleting frames run Lisp code? If so, can we get rid of that?
59 It is a dangerous design.
60 http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg01330.html
62 ** Why were the calls to x_fully_uncatch_errors commented out in eval.c?
63 http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg01987.html
65 ** rms: gnus-dired.el is a mistake. Those features should not
66 be part of Gnus. They should be moved to some other part of Emacs.
67 rsteib: Gnus dependencies in `gnus-dired.el' (and `mailcap.el') have been
68 minimized. I don't know what is left to do here.
70 ** Check for modes which bind M-s that conflicts with a new global binding M-s
71 and change key bindings where necessary. The current list of modes:
73 1. Gnus binds `M-s' to `gnus-summary-search-article-forward'.
75 2. Minibuffer binds `M-s' to `next-matching-history-element'
76 (not useful any more since C-s can now search in the history).
78 3. Shell mode binds `M-s' to `comint-next-matching-input'.
79 This key binding can be changed later when we will implement
80 incremental search through the shell history.
82 4. `center-line' in Text mode was already moved to the text formatting
83 keymap as `M-o M-s' (thus this binding is not necessary any more
84 in `nroff-mode-map' too and can be removed now from the nroff mode
85 because it can now use the global key binding `M-o M-s' `center-line').
87 5. PCL-CVS binds `M-s' to `cvs-status', and log-edit-mode binds it to
88 `log-edit-comment-search-forward'. Perhaps search commands
89 on the global key binding `M-s' are useless in these modes.
91 ** sdl.web@gmail.com, 30 Oct: ps-lpr-switches has no effect
92 http://lists.gnu.org/archive/html/emacs-devel/2007-10/msg02091.html
96 2007-11-09 Vinicius Jose Latorre <viniciusjl@ig.com.br>
99 (ps-do-despool): If ps-lpr-switches is not a list, force it to be one.
101 ** In C, use EMACS_INT for variables and structure members
102 for buffer/string positions. E.g. struct it, struct text_pos.
106 ** Clean up Emacs.app references in code and documentation.
108 ** Document new font backend
110 ** Document XEmbed support
112 ** Check the Emacs Tutorial.
114 The first line of every tutorial must begin with text ending in a
115 period (".", ASCII 0x2E) saying "Emacs Tutorial" in the respective
116 language. This should be followed by "See end for copying conditions",
117 likewise in the respective language.
119 After each file name, on the same line or the following line, come the
120 names of the people who have checked it.
123 ----------------------------------
124 etc/TUTORIAL rgm (but see Bug#3783)
128 etc/TUTORIAL.de Werner Lemberg
169 fortran-xtra.texi -- rgm
176 macos.texi -- davidswelt
177 maintaining.texi -- cyd
183 msdog-xtra.texi -- eliz
191 sending.texi -- rgm (maybe needs some brief mailclient.el details in
192 "Mail Sending" section?)
195 windows.texi -- rudalics
196 xresources.texi -- cyd
198 ** Check the Lisp manual.
209 customize.texi -- cyd
210 debugging.texi -- cyd
218 functions.texi -- cyd
223 internals.texi -- cyd
238 positions.texi -- cyd
240 searching.texi -- cyd
241 sequences.texi -- cyd
248 variables.texi -- cyd
249 windows.texi -- rudalics
253 ** CEDET (not for 23.1 due to paperwork issues, perhaps for 23.2)
255 ** pov-mode (probably not for Emacs-23: waiting for a Free POV-Ray).