Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
emacs
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
1
Issues
1
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
emacs
emacs
Commits
10a99e0d
Commit
10a99e0d
authored
Jul 11, 2009
by
Glenn Morris
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Comments on manual checking.
parent
e538d479
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
22 additions
and
2 deletions
+22
-2
admin/FOR-RELEASE
admin/FOR-RELEASE
+22
-2
No files found.
admin/FOR-RELEASE
View file @
10a99e0d
...
...
@@ -2,8 +2,26 @@ Tasks needed before the next release.
* TO BE DONE SHORTLY BEFORE RELEASE
** Check for widow and orphan lines in manuals;
make sure all the pages really look ok in the manual as formatted.
** Manuals
Check cross-references between the manuals (eg from emacs to elisp)
are correct. (Is there an automated way to do this?)
make emacs.dvi, elisp.dvi, and deal with any errors (undefined
references etc) in the output. Break any overfull lines.
Underfull hboxes are not serious, but it can be nice to get rid of
them if a simple rephrasing or rearrangement will work.
Update the master menu and detailed menu (eg the antinews version).
The command texinfo-multiple-files-update can do this, but you
probably want to apply the results selectively (eg the current master
menu has better line-breaks than the automatic version). It includes
the menu-entry name (if there is one) as well as the node name - using
only the latter looks better. Also, it doesn't seem to handle nested
includes, so will miss edebug.texi etc.
Check for widow and orphan lines; make sure all the pages really look
ok in the manual as formatted. (AFAIK, there is no way to do this
except paging through the whole manual.)
** Regenerate the pdf versions of the reference cards in etc/refcards/.
...
...
@@ -24,6 +42,8 @@ sk Miroslav Vaško
** Try to reorder NEWS: most important things first, related items together.
** Consider bumping customize-changed-options-previous-release.
* BUGS
** Does deleting frames run Lisp code? If so, can we get rid of that?
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment