|author||Yoni Rabkin <email@example.com>||2020-11-15 21:01:23 -0500|
|committer||Yoni Rabkin <firstname.lastname@example.org>||2020-11-15 21:01:23 -0500|
move to other machineunchanges
2 files changed, 31 insertions, 2 deletions
@@ -1,3 +1,8 @@
+New in version 1.31
New in version 1.0:
* Upgrade to GPLv3 (with the kind permission of the people from
diff --git a/doc/developer-release.txt b/doc/developer-release.txt
index e976f0b..bab477d 100644
@@ -1,13 +1,37 @@
-*- outline -*-
-* Notes for preparing a release for rt-liberation
+This is an outline of how to make a release for rt-liberation via GNU
In order for the ELPA system to trigger a release the version number
in the comment header of rt-liberation.el must be incremented.
+Update the NEWS file to tell all of the people the Good News.
+Push these updates to the git repo.
+Tag the release with the ELPA version number:
+ $ git tag -a 1.31 -m "1.31"
+Then push that tag to the VCS:
+ $ git push --tags origin "1.31"
+Update the manual, compile it, and update the copy of the info file in
+the root directory so that ELPA can install it.
After each manual update the info file needs to be copied into the
root of the project so that ELPA can pick it up.