summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJens Georg <mail@jensge.org>2014-09-21 17:57:47 +0200
committerJens Georg <mail@jensge.org>2014-09-21 17:58:05 +0200
commit2190dcb9f1d53077a27308a5fbeb5876e19258b6 (patch)
tree7f11e00558c51e910e08ef05399a2bb8261ce34b
parentd6a43bf895e8a6a23ef2e5533f435102b92c506a (diff)
downloadgupnp-2190dcb9f1d53077a27308a5fbeb5876e19258b6.tar.gz
Remove obsolete README.release
Signed-off-by: Jens Georg <mail@jensge.org>
-rw-r--r--README.release16
1 files changed, 0 insertions, 16 deletions
diff --git a/README.release b/README.release
deleted file mode 100644
index ba3aa9d..0000000
--- a/README.release
+++ /dev/null
@@ -1,16 +0,0 @@
-
-Releasing a GUPnP component:
-1. Ensure version in configure.ac is correct, update NEWS
-2. make distcheck
-3. Commit, create svn tag <COMPONENT-NAME>-<MAJOR>_<MINOR>[_<BUILD>]
-4. Bump version number to a 'post-release' version
-5. If you do not have actual release privileges, inform
- someone who does (mailing list is fine).
-
-With release privileges:
-6. Upload documentation via WebDAV (if needed):
- https://svn.o-hand.com/sources/gupnp-docs/
-7. update tarball and website NEWS via SVN:
- https://svn.o-hand.com/repos/gupnp-web
-
-8. Send announcement to mailing list on behalf of the releaser