1 Tasks needed before the next release.
3 * TO BE DONE SHORTLY BEFORE RELEASE
5 ** Check for widow and orphan lines in manuals;
6 make sure all the pages really look ok in the manual as formatted.
8 ** Regenerate the pdf versions of the reference cards in etc/refcards/.
10 ** Ask maintainers of refcard translations to update them.
14 LANG Translator Status
23 ** Remove temporary +++/--- lines in NEWS.
25 ** Try to reorder NEWS: most important things first, related items together.
27 * WINDOWS SUPPORT BUGS
29 These don't need to be fixed before a release, but we call the
30 attention of Windows users to fixing them.
32 ** Drew Adams 12 Aug bug rpt: overlay display artifact: trace left behind
33 Windows only bug. Bug appears only when Cleartype enabled, probably related
34 to the hack introduced on 2005-07-01 to fix some other Cleartype problem.
36 ** henman@it.to-be.co.jp 09 Aug 2006: ispell.el problem on Cygwin.
37 (Did we decide that is unreproducible?)
39 * BUGS WAITING FOR MORE USER INPUT
41 ** raman@users.sf.net, sep 7: Emacs 23.0.50: Segfaults in alloc.c (batch process)
42 http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg00690.html
44 ** undefined reference getopt_long
45 Report by Daniel C. Bastos <dbast0s@yahoo.com.br> on bug-gnu-emacs
46 from 2007-08-27. Impossible to procede without more input from OP (as
47 of 20070912, emails are bouncing) or someone else who can reproduce this.
48 http://lists.gnu.org/archive/html/emacs-devel/2007-08/msg01497.html
50 ** emacs-22.1 with GTK problems (with patches)
51 Only outstanding issue seems to be whether Solaris 2.6 GTK can be
52 supported in the absence of recursive mutexes, via a change to
53 alloc.c, or whether configure should abort.
54 http://lists.gnu.org/archive/html/bug-gnu-emacs/2007-09/msg00055.html
58 ** Document the changes introduced by multi-tty
59 http://lists.gnu.org/archive/html/emacs-devel/2007-08/msg01639.html
60 http://lists.gnu.org/archive/html/emacs-devel/2007-08/msg01602.html
62 ** Does deleting frames run Lisp code? If so, can we get rid of that?
63 It is a dangerous design.
64 http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg01330.html
66 ** Why were the calls to x_fully_uncatch_errors commented out in eval.c?
67 http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg01987.html
69 ** grep et al should use font-lock to do highlighting, so that they respect font-lock-mode.
70 "can't turn off font-lock"
71 http://lists.gnu.org/archive/html/emacs-devel/2007-08/msg00548.html
73 ** mah@everybody.org, Sep 18: erc causes emacs to hang with multi-tty
74 http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg01765.html
76 ** jbw@macs.hw.ac.uk, Sep 18: before-string property has no effect if display property is empty
77 http://lists.gnu.org/archive/html/bug-gnu-emacs/2007-09/msg00094.html
78 http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg01816.html
80 ** sdl.web@gmail.com, Sep 24: TLS infinite loop.
81 http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg01720.html
83 ** herring@lanl.gov: find-func: can no longer find adviced subrs
86 ** \\{...} produces duplicate entries
87 http://lists.gnu.org/archive/html/emacs-devel/2007-05/msg00209.html
89 ** menu indications of key bindings for remapped commands
90 http://lists.gnu.org/archive/html/emacs-devel/2007-05/msg01339.html
92 ** tromey@redhat.com: two View-mode "quit" bugs
93 http://lists.gnu.org/archive/html/emacs-devel/2007-07/msg00103.html
95 ** rms: gnus-dired.el is a mistake. Those features should not
96 be part of Gnus. They should be moved to some other part of Emacs.
98 ** C-x v v no longer works the way it used to
99 http://lists.gnu.org/archive/html/emacs-devel/2007-10/msg00785.html
101 ** vc-diff no longer works the way it used to
102 http://lists.gnu.org/archive/html/emacs-devel/2007-10/msg01753.html
103 (vc-revert also needs the repository now with CVS)
105 ** sdl.web@gmail.com, 28 Oct: window-system in face definition
107 ** add README files for etc/gnus, etc/images/smilies/medium,grayscale
108 update etc/images README files with any new images
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 ----------------------------------