Back to version 2.0.1, updated documentation.

git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@1883 280ebfd0-de03-0410-8827-d642c229c3f4

1 files changed, 7 insertions, 5 deletions

diff --git a/README.dev b/README.dev
index 9b4a7e481..3c8513238 100644
--- a/README.dev
+++ b/README.dev
@@ -7,16 +7,18 @@ 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): rcs2log > ChangeLog.2
+  1) Check the version and update the date in mpfr.texi.
+  2) 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
+  3) Generate the release version with "make dist".
+  4) 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
+  5) 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): cvs tag mpfr-2-0-1-rel
-  5) Update the VERSION file to indicate the next version.
+  6) Update the VERSION file to indicate the next version.
+     Update the version in mpfr.texi.
 
 When submitting patches, unified diffs (option -u) are recommended,
 as they are more readable. You can also use the option -d to generate