diff options
| author | Yoni Rabkin <yoni@rabkins.net> | 2020-09-22 17:11:37 -0400 |
|---|---|---|
| committer | Yoni Rabkin <yoni@rabkins.net> | 2020-09-22 17:11:37 -0400 |
| commit | e2891f2740f54b31c1a6741dda6df5c0be1f3be6 (patch) | |
| tree | 228c262428636bc0c06ffb7f210ba8c6b769defa | |
| parent | 36d760e2bd7e5376aff3f03456fa6445833242ad (diff) | |
* doc/developer-release.txt: elpa notes
| -rw-r--r-- | doc/developer-release.txt | 9 |
1 files 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 -release. +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 |