summaryrefslogtreecommitdiff
path: root/admin/release-process
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2016-02-03 17:13:04 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2016-02-03 17:20:17 -0800
commit91557f5e2decb723544a703d01f11879be07fd04 (patch)
tree8f53ef75492e0552746c3f9a6da5b1efbc051b0e /admin/release-process
parent2c0dc9fa70dcde56f68db6e72309f995e5c0e6e0 (diff)
downloademacs-91557f5e2decb723544a703d01f11879be07fd04.tar.gz
Quoting fixes in doc strings and diagnostics
* lisp/emacs-lisp/bytecomp.el (byte-compile-setq, byte-compile-funcall): * lisp/gnus/mml-smime.el (mml-smime-get-dns-cert) (mml-smime-get-ldap-cert): Follow user style preference when quoting diagnostics.
Diffstat (limited to 'admin/release-process')
-rw-r--r--admin/release-process18
1 files changed, 9 insertions, 9 deletions
diff --git a/admin/release-process b/admin/release-process
index 5a95fa2d7bc..2f23dac9b7f 100644
--- a/admin/release-process
+++ b/admin/release-process
@@ -7,7 +7,7 @@ Each release cycle will be split into two periods.
** Phase one: development
The first phase of the release schedule is the "heads-down" working
-period for new features, on the `master' branch and several feature
+period for new features, on the 'master' branch and several feature
branches.
** Phase two: fixing and stabilizing the release branch
@@ -23,11 +23,11 @@ new features.
At the beginning of this phase, a release branch called "emacs-NN"
("NN" represents the major version number of the new Emacs release)
-will be cut from `master'. When that happens, the version number on
-`master' should be incremented; use admin/admin.el's `set-version'
+will be cut from 'master'. When that happens, the version number on
+'master' should be incremented; use admin/admin.el's 'set-version'
command to do that, then commit the changes it made and push to
-`master'. For major releases, also update the value of
-`customize-changed-options-previous-release'.
+'master'. For major releases, also update the value of
+'customize-changed-options-previous-release'.
The 2 main manuals, the User Manual and the Emacs Lisp Manual, need to
be proofread, preferably by at least 2 different persons, and any
@@ -35,7 +35,7 @@ uncovered problems fixed. This is a lot of work, so it is advisable
to divide the job between several people (see the checklist near the
end of this file).
-In parallel to this phase, `master' can receive new features, to be
+In parallel to this phase, 'master' can receive new features, to be
released in the next release cycle. From time to time, the master
branches merges bugfix commits from the "emacs-NN" branch.
@@ -55,7 +55,7 @@ Change "block" to "unblock" to unblock the bug.
* TO BE DONE SHORTLY BEFORE RELEASE
** Make sure the Copyright date reflects the current year in the source
-files. See `admin/notes/years' for information about maintaining
+files. See 'admin/notes/years' for information about maintaining
copyright years for GNU Emacs.
** Make sure the necessary sources and scripts for any generated files
@@ -344,10 +344,10 @@ windows.texi
* OTHER INFORMATION
-For Emacs's versioning scheme, see `admin/notes/versioning'.
+For Emacs's versioning scheme, see 'admin/notes/versioning'.
For instructions to create pretest or release tarballs, announcements,
-etc., see `admin/make-tarball.txt'.
+etc., see 'admin/make-tarball.txt'.
Local variables: