From 71041fb322ca6ef428ec68c23ae058bc39384450 Mon Sep 17 00:00:00 2001 From: Michael Roitzsch Date: Sun, 21 Dec 2003 14:09:46 +0000 Subject: a note about release-check and a typo fix CVS patchset: 5931 CVS date: 2003/12/21 14:09:46 --- doc/internal/HOWTO.release | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'doc/internal/HOWTO.release') 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: -- cgit v1.2.3