summaryrefslogtreecommitdiff
path: root/doc/internal/HOWTO.release
diff options
context:
space:
mode:
authorMichael Roitzsch <mroi@users.sourceforge.net>2003-12-21 14:09:46 +0000
committerMichael Roitzsch <mroi@users.sourceforge.net>2003-12-21 14:09:46 +0000
commit71041fb322ca6ef428ec68c23ae058bc39384450 (patch)
treec07347a293aa550e09c9149ef3b7ff0b2e24a367 /doc/internal/HOWTO.release
parent455406a88489f8c6f45fde00a2043af0c2c980dd (diff)
downloadxine-lib-71041fb322ca6ef428ec68c23ae058bc39384450.tar.gz
xine-lib-71041fb322ca6ef428ec68c23ae058bc39384450.tar.bz2
a note about release-check and a typo fix
CVS patchset: 5931 CVS date: 2003/12/21 14:09:46
Diffstat (limited to 'doc/internal/HOWTO.release')
-rw-r--r--doc/internal/HOWTO.release4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/internal/HOWTO.release b/doc/internal/HOWTO.release
index 6cd74b74e..5d0179c8d 100644
--- a/doc/internal/HOWTO.release
+++ b/doc/internal/HOWTO.release
@@ -39,6 +39,8 @@ Currently, best practice to get a release out looks like this:
identify at least one dedicatet tester for each feature.
So check that overview! Ask testers to test if their feature is
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
- does "make dist" produce a complete (ie. compilable) tarball
(note: nightly build logs will tell you this.)
@@ -108,7 +110,7 @@ hands.
release. Copy&paste all ChangeLog entries for this release into the
announcement. Make sure you have GPG clearsigned the announcement when
sending it!
- (also make sure it gets immediately approved by the aine-announce
+ (also make sure it gets immediately approved by the xine-announce
moderator!)
12) write the announcement for xinehq: