diff options
author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2015-08-19 08:05:38 +0000 |
---|---|---|
committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2015-08-19 08:05:38 +0000 |
commit | a227948da60e86331ad5db76dcec77dd39d67288 (patch) | |
tree | 3d45875d94bf8ccf7375ed6dc22248f6999193b5 | |
parent | dda8bdd4a8c4a112c06bf8c0e3960046a11d0ea7 (diff) | |
download | mpfr-a227948da60e86331ad5db76dcec77dd39d67288.tar.gz |
[doc/README.dev] "To make a release": mention abi-compliance-checker.
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@9642 280ebfd0-de03-0410-8827-d642c229c3f4
-rw-r--r-- | doc/README.dev | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/README.dev b/doc/README.dev index 261d04de4..eb584800b 100644 --- a/doc/README.dev +++ b/doc/README.dev @@ -174,8 +174,14 @@ To make a release (for the MPFR team): 3) Update the NEWS file, in particular say if the release is binary and/or API compatible (or not) with previous releases. Also update the "API Compatibility" section in the manual (mpfr.texi). + Check with abi-compliance-checker (ABI Compliance Checker)[*], on the + latest MPFR releases built with no configure options (except --prefix), + that no changes have been missed. Note that abi-compliance-checker can + only check the symbols, types and constants; it cannot detect just a + change in the behavior, thus may miss some incompatibilities. Update the FAQ.html file with update-faq (and check it) in the doc directory. + [*] http://lvc.github.io/abi-compliance-checker/ 4) Update the ChangeLog file with "TZ=UTC svn log -rHEAD:0 -v" in UTF-8 locales, e.g. "LC_ALL=en_US.UTF8 TZ=UTC svn log -rHEAD:0 -v". |