From fb68f74a497855cd15d3e2085275d8b6b4de95cd Mon Sep 17 00:00:00 2001 From: vlefevre Date: Thu, 11 Jun 2020 15:07:52 +0000 Subject: [doc/README.dev] Updated "To make a release". git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@13986 280ebfd0-de03-0410-8827-d642c229c3f4 --- doc/README.dev | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/README.dev b/doc/README.dev index accbfad1c..3c887b992 100644 --- a/doc/README.dev +++ b/doc/README.dev @@ -127,17 +127,19 @@ To make a release (for the MPFR team): *** Please read this section entirely before making any release. *** - 0) For a non-patchlevel release, before creating a branch from the trunk, - some operations should be done: + 0) For a non-patchlevel release, before creating a branch from the trunk + (or more often), some operations should be done: * make sure that the src/mpfr-longlong.h file (from GMP's longlong.h) is up-to-date (updates could also be done in patchlevel releases, but with care); + * among the checks below, those that are most likely to notice issues, + as it is easy to forget something; + * in particular, check that the abi-compliance-checker output, + the "API Compatibility" section of the manual (mpfr.texi), and + the NEWS file are consistent; * update the libtool version (see src/Makefile.am) and the DLL version (see configure.ac) if need be, though this should have been done as soon as the ABI changed in the trunk; - * among the checks below, those that are most likely to notice issues, - e.g. abi-compliance-checker and the "API Compatibility" section in - the manual (mpfr.texi), as it is easy to forget something; * update the ChangeLog (see below) in the trunk, in order to minimize the future diffs. If everything is OK, create the branch. Then: -- cgit v1.2.1