diff options
author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2003-10-16 12:48:40 +0000 |
---|---|---|
committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2003-10-16 12:48:40 +0000 |
commit | 0673bcf31ade59fbc69119ab5bed479fc25bedf9 (patch) | |
tree | 35aed94a77d5fd7e763fb9fed7065ca3bffe7f54 | |
parent | ea6ca61c5694de836ddbec06a85a01d8caaa90d0 (diff) | |
download | mpfr-0673bcf31ade59fbc69119ab5bed479fc25bedf9.tar.gz |
Update.
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@2505 280ebfd0-de03-0410-8827-d642c229c3f4
-rw-r--r-- | README.dev | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/README.dev b/README.dev index 1ee77630b..bfc843de2 100644 --- a/README.dev +++ b/README.dev @@ -40,10 +40,13 @@ To make a release (for the MPFR team): the duplicated lines. 3) Generate the release version with "make dist". 4) Test the release version on different machines, with and without - the --disable-alloca configure option (or compile gmp with - --enable-alloca=debug). + the --disable-alloca configure option (or compile gmp with + --enable-alloca=debug), with and without -DXDEBUG in $CFLAGS. 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 6) Update the VERSION file to indicate the next version. Update the version in mpfr.texi. + +A branch may be created first (e.g. with "cvs tag -b mpfr-2-0-2-branch") +to allow new features to be committed to the trunk. |