| 1 |
1. Ensure that all important user-facing changes are mentioned |
| 2 |
in the ChangeLog. |
| 3 |
|
| 4 |
2. Run the tests with the "--with-pari", "--enable-precision=double-double", |
| 5 |
and "--enable-precision=quad-double" configure flags. The "make check" |
| 6 |
suite should pass with all of them. |
| 7 |
|
| 8 |
3. If libLfunction has changed, update the -version-info in its Makefile.am |
| 9 |
according to the "Updating library version information" section of |
| 10 |
https://www.gnu.org/software/libtool/manual/libtool.html |
| 11 |
|
| 12 |
4. Update the package version number in configure.ac. |
| 13 |
|
| 14 |
5. Build a release tarball. First, run `git clean -x -f -d` to ensure |
| 15 |
that you're starting fresh. Then run `autoreconf -fi` to regenerate |
| 16 |
all of the autotools files. Run `./configure` to create your |
| 17 |
Makefiles, and finally, `make dist` to create the release tarball. |
| 18 |
|
| 19 |
6. Run `make distcheck` to ensure that the release tarball works. |
| 20 |
|
| 21 |
7. Tag the commit that corresponds to the release with `git tag -s |
| 22 |
<version-number>`. |
| 23 |
|
| 24 |
8. Upload the release tarball (from step 5) to Gitlab. |