[elpa] externals/rt-liberation 291a8e3 20/68: move to other machine

[Yoni Rabkin]

branch: externals/rt-liberation
commit 291a8e377fab357a99772f814c48075d0e06a028
Author: Yoni Rabkin <yoni@rabkins.net>
Commit: Yoni Rabkin <yoni@rabkins.net>

    move to other machine
---
 NEWS                      |  5 +++++
 doc/developer-release.txt | 28 ++++++++++++++++++++++++++--
 2 files changed, 31 insertions(+), 2 deletions(-)

diff --git a/NEWS b/NEWS
index 9a75035..312281f 100644
--- a/NEWS
+++ b/NEWS
@@ -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
--- 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.