procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; * admin/release-process: Move etc/HISTORY from here...

Browse source 
; * admin/make-tarball.txt: ... to here.
This commit is contained in:
Glenn Morris 2016-05-24 13:00:57 -04:00
parent bea1b65b3c
commit 906c810158
2 changed files with 10 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
admin/make-tarball.txt
View file

@ -51,24 +51,23 @@ General steps (for each step, check for possible errors):
Commit any fixes to authors.el. Commit any fixes to authors.el.
3. Set the version number (M-x load-file RET admin/admin.el RET, then 3. Set the version number (M-x load-file RET admin/admin.el RET, then
M-x set-version RET). For a release, add released ChangeLog M-x set-version RET). For a pretest, start at version .90. After
entries (create a ChangeLog symlink a la vc-dwim, then run M-x .99, use .990 (so that it sorts).
add-release-logs RET, then run the shell command 'vc-dwim --commit').
For a pretest, start at version .90. After .99, use .990 (so that
it sorts).
The final pretest should be a release candidate. Set the version The final pretest should be a release candidate. Set the version
number to that of the actual release. Pick a date about a week number to that of the actual release. Pick a date about a week
from now when you intend to make the release. Use vc-dwim and from now when you intend to make the release. Use M-x
M-x add-release-logs as described above to add commit messages add-release-logs to add entries to etc/HISTORY and the ChangeLog
that will appear in the tarball's automatically-generated ChangeLog file. It's best not to commit these files until the release is
file as entries for that date. actually made. Merge the entries from (unversioned) ChangeLog
into the top of the current versioned ChangeLog.N and commit that
along with etc/HISTORY. Then you can tag that commit as the
release.
Name the tar file as emacs-XX.Y-rc1.tar. If all goes well in the Name the tar file as emacs-XX.Y-rc1.tar. If all goes well in the
following week, you can simply rename the file and use it for the following week, you can simply rename the file and use it for the
actual release. If you need another release candidate, remember actual release. If you need another release candidate, remember
to adjust the ChangeLog entries. to adjust the ChangeLog and etc/HISTORY entries.
If you need to change only a file(s) that cannot possibly affect If you need to change only a file(s) that cannot possibly affect
the build (README, ChangeLog, NEWS, etc.) then rather than doing the build (README, ChangeLog, NEWS, etc.) then rather than doing

2
admin/release-process
View file

@ -83,8 +83,6 @@ documentation (or decide no updates are necessary) for those that aren't.
** cusver-check from admin.el can help find new defcustoms missing ** cusver-check from admin.el can help find new defcustoms missing
:version tags. :version tags.
** Add a line to etc/HISTORY for the release version number and date.
** Manuals ** Manuals
Check for node names using problematic characters: Check for node names using problematic characters:
find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} + find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} +