[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[elpa] externals/emms e2891f2 02/11: * doc/developer-release.txt: elpa n

From: Yoni Rabkin
Subject: [elpa] externals/emms e2891f2 02/11: * doc/developer-release.txt: elpa notes
Date: Tue, 27 Oct 2020 15:08:27 -0400 (EDT)

branch: externals/emms
commit e2891f2740f54b31c1a6741dda6df5c0be1f3be6
Author: Yoni Rabkin <yoni@rabkins.net>
Commit: Yoni Rabkin <yoni@rabkins.net>

    * doc/developer-release.txt: elpa notes
 doc/developer-release.txt | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/doc/developer-release.txt b/doc/developer-release.txt
index 65fc8ab..be70e22 100644
--- a/doc/developer-release.txt
+++ b/doc/developer-release.txt
@@ -1,11 +1,12 @@
-This file tries to list the things people have to do before they do a
+This is an explanation of how to make a release for Emms. Emms is
+currently distributed in three different ways: via the Git repo on
+Savannah, as a tarball from GNU, and via GNU ELPA.
 *  Increase the version number in emms.el (variable, elpa header), Makefile
 *  Update NEWS
-*  Push version updates to git repo.
+*  Push version updates to git repo
 *  Tag release in VCS, for example `git tag -a 4.2 -m "4.2"'
@@ -19,4 +20,6 @@ release.
 *  Update website
+*  Push to GNU ELPA: push to the Savannah "elpa" branch, and from there "git 
push elpa elpa:refs/heads/externals/emms"
 *  Send announcement email to gnu-info and to the emms mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]