[elpa] externals/emms dd301fb 02/80: * doc/developer-release.txt:

[Stefan Monnier]

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

    * doc/developer-release.txt:
---
 doc/developer-release.txt | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/doc/developer-release.txt b/doc/developer-release.txt
index a09081b..f197742 100644
--- a/doc/developer-release.txt
+++ b/doc/developer-release.txt
@@ -1,23 +1,19 @@
 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.
+developed at Savannah (https://savannah.gnu.org/projects/emms/) and
+distributed via Emacs ELPA (https://elpa.gnu.org/).
 
 * Increase the version number in emms.el (variable, elpa header), Makefile
 
 * Update NEWS
 
-* Push version updates to git repo
+* Update the manual, then copy compiled emms.info to root directory
+
+* Push version updates to VCS
 
 * Tag release in VCS, for example `git tag -a 4.2 -m "4.2"'
 
 * Push tag to VCS if needed, for example `git push --tags origin "4.2"'
 
-* Run make release
-
-* Run make upload
-
-* Update copy of emms.info in root directory
-
 * Update online manual (cvs commit -m "update manual" manual/index.html)
 
 * Update website (cvs commit -m "update website" index.html)