summaryrefslogtreecommitdiff
path: root/doc/internal/HOWTO.release
diff options
context:
space:
mode:
Diffstat (limited to 'doc/internal/HOWTO.release')
-rw-r--r--doc/internal/HOWTO.release8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/internal/HOWTO.release b/doc/internal/HOWTO.release
index 5d0179c8d..46d97215d 100644
--- a/doc/internal/HOWTO.release
+++ b/doc/internal/HOWTO.release
@@ -41,6 +41,14 @@ Currently, best practice to get a release out looks like this:
marked "untested".
- you might want to run "make release-check", it will tell you about files
from CVS missing in the release; be sure to check these
+
+ OR
+
+ you might want to run "make distcheck", this will test the
+ packaging, building, and testing of all xine-lib. This will
+ alert you to any missing files from the tarball or problems
+ in the Makefile rules.
+
- does "make dist" produce a complete (ie. compilable) tarball
(note: nightly build logs will tell you this.)