summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorYoni Rabkin <yoni@rabkins.net>2020-11-15 21:01:23 -0500
committerYoni Rabkin <yoni@rabkins.net>2020-11-15 21:01:23 -0500
commit291a8e377fab357a99772f814c48075d0e06a028 (patch)
tree2e6bfb63e3dfcfe7d360a76b9ed693c86b1c3650 /doc
parent9902111423f393c4c0079feb4f51dfe425173b00 (diff)
move to other machineunchanges
Diffstat (limited to 'doc')
-rw-r--r--doc/developer-release.txt28
1 files changed, 26 insertions, 2 deletions
diff --git a/doc/developer-release.txt b/doc/developer-release.txt
index e976f0b..bab477d 100644
--- a/doc/developer-release.txt
+++ b/doc/developer-release.txt
@@ -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
+ELPA.
-** Version
+* version
In order for the ELPA system to trigger a release the version number
in the comment header of rt-liberation.el must be incremented.
+* NEWS
+Update the NEWS file to tell all of the people the Good News.
+
+
+* push
+Push these updates to the git repo.
+
+
+* tag
+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"
+
+
+* documentation
+Update the manual, compile it, and update the copy of the info file in
+the root directory so that ELPA can install it.
+
+
** Info
After each manual update the info file needs to be copied into the
root of the project so that ELPA can pick it up.