From 0a8d56c8e7316023ace9cacfd4c6b16cf9fde857 Mon Sep 17 00:00:00 2001 From: vlefevre Date: Mon, 15 Apr 2002 14:48:58 +0000 Subject: Post-release commit. git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@1882 280ebfd0-de03-0410-8827-d642c229c3f4 --- README.dev | 6 ++++-- VERSION | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/README.dev b/README.dev index c48ea36ed..9b4a7e481 100644 --- a/README.dev +++ b/README.dev @@ -7,13 +7,15 @@ date in the yyyymmdd format must be added to the version number, for instance: "2.0.1-20020319". To make a release: - 1) Update the ChangeLog file (using rcs2log). + 1) Update the ChangeLog file (using rcs2log): rcs2log > ChangeLog.2 + and edit ChangeLog to insert ChangeLog.2 at the beginning and + remove the duplicated lines. 2) Generate the release version with "make dist". 3) Test the release version on different machines, with and without the --disable-alloca configure option. 4) If there is no problem, add a tag to the CVS corresponding to the release, e.g. mpfr-2-0-1-rel for mpfr 2.0.1 (note that the periods - are replaced by dashes). + are replaced by dashes): cvs tag mpfr-2-0-1-rel 5) Update the VERSION file to indicate the next version. When submitting patches, unified diffs (option -u) are recommended, diff --git a/VERSION b/VERSION index 38f77a65b..e9307ca57 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -2.0.1 +2.0.2 -- cgit v1.2.1