branch: externals/emms
commit ef1ad535d29c9b59505d58babd99847c17ab05b3
Author: Yoni Rabkin <y...@rabkins.net>
Commit: Yoni Rabkin <y...@rabkins.net>
* doc/devel/developer-release.txt: move file
---
doc/devel/developer-release.txt | 64 +++++++++++++++++++++++++++++++++++++++++
doc/developer-release.txt | 34 ----------------------
2 files changed, 64 insertions(+), 34 deletions(-)
diff --git a/doc/devel/developer-release.txt b/doc/devel/developer-release.txt
new file mode 100644
index 0000000000..eaf99be3d7
--- /dev/null
+++ b/doc/devel/developer-release.txt
@@ -0,0 +1,64 @@
+-*- outline -*-
+This is an explanation of how to make a release for Emms. Emms is
+developed at Savannah (https://savannah.gnu.org/projects/emms/) and
+distributed via Emacs ELPA (https://elpa.gnu.org/).
+
+* clean compilation
+Check for clean compilation on the two latest major Emacs releases.
+
+
+* check for basic functionality
+Check for clean loading and running with basic functionality on the
+two latest major Emacs releases.
+
+
+* version bump
+Increase the version number in emms.el (`emms-version' and the elpa
+header as a comment).
+
+
+* NEWS
+update the NEWS file from the git log to include all significant
+user-facing changes.
+
+
+* contributors
+Update AUTHORS file with the names of any new contributors. This is a
+good chance to make sure we are releasing everything with proper
+copyleft.
+
+
+* update the manual
+Update the manual:
+
+ $ makeinfo --html --no-split emms.texinfo
+
+Make sure that the manual compiles cleanly and that it looks right.
+
+
+* website update
+Update the website with all any pertinent information. Upload a new
+version of the manual if it has changed in this release:
+
+ $ cvs commit -m "update website" index.html
+
+
+* tag release
+Tag the release in git, for example:
+
+ $ git tag -a 4.2 -m "4.2"
+
+
+* push tag
+Push the tag to the git repo, for example:
+
+ $ git push --tags origin "4.2"
+
+
+* push to repo
+Push the version update itself to the git repo. We have automatic
+synchronization set up for GNU ELPA, so we are done.
+
+
+* announce
+Announce the release in the emms mailing list if it is called for.
diff --git a/doc/developer-release.txt b/doc/developer-release.txt
deleted file mode 100644
index 0031a1f175..0000000000
--- a/doc/developer-release.txt
+++ /dev/null
@@ -1,34 +0,0 @@
-This is an explanation of how to make a release for Emms. Emms is
-developed at Savannah (https://savannah.gnu.org/projects/emms/) and
-distributed via Emacs ELPA (https://elpa.gnu.org/).
-
-* Check for clean compilation on the two latest major Emacs releases.
-
-* Check for clean running of basic functionality on the two latest
- major Emacs releases.
-
-* Increase the version number in emms.el (variable, elpa header).
-
-* Update NEWS.
-
-* Update AUTHORS file with the names of any new contributors.
-
-* Update the manual (makeinfo --html --no-split emms.texinfo).
-
-* Update website (cvs commit -m "update website" index.html).
-
-* Tag release in VCS, for example `git tag -a 4.2 -m "4.2"'.
-
-* Push tag to VCS, for example `git push --tags origin "4.2"'.
-
-* Push version updates to VCS.
-
-* If automatic syncronization is enabled then we are done. Otherwise:
-
- * Push to GNU ELPA:
-
- - merge master into the Savannah "elpa" branch and push to Savannah
-
- - from the "elpa" branch in Savannah push to elpa.git: "git push
elpa elpa:externals/emms"
-
-* Send announcement email to the emms mailing list if needed.
