From d2c999398f27c32a0655b372bdccebd329817876 Mon Sep 17 00:00:00 2001 From: Pavel Roskin Date: Thu, 24 Oct 2002 16:58:01 +0000 Subject: [PATCH] Add release procedure. --- maint/RELEASE_PROCEDURE | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 maint/RELEASE_PROCEDURE diff --git a/maint/RELEASE_PROCEDURE b/maint/RELEASE_PROCEDURE new file mode 100644 index 000000000..2bf3007a5 --- /dev/null +++ b/maint/RELEASE_PROCEDURE @@ -0,0 +1,27 @@ +This document describes step by step the release procedure of GNU +Midnight Commander. + + +Announce the intention to release the next version in both mailing lists +at least 3 days before the release date, unless it's a security release. + +Make sure that all significant user-visible changes are in the NEWS +file. Group changes by topics to improve readability. + +Review the English version of the manual and fix it if necessary. + +Check dates in all manuals and update them if significant changes have +been done since the previous release. + +Make sure that maint/mctest covers most features of the current code and +run it on a clean working directory. + +Review files with stdout and stderr from every build. Make sure that +all warnings (if any) are caused by other software and cannot be avoided +without significant damage to the code. + +Upload the resulting tarball and binary packages to login.ibiblio.org. + +Change the homepage to mention the new version. + +Announce the release in both mailing lists.