GNU Astronomy Utilities
11.8 Developer’s checklist
This is a checklist of things to do after applying your changes/additions
- If the change is non-trivial, write test(s) in the tests/progname/
directory to test the change(s)/addition(s) you have made. Then add their
file names to tests/Makefile.am.
$ make check to make sure everything is working correctly.
- Make sure the documentation (this book) is completely up to date with your
changes, see Documentation.
- Commit the change to your issue branch (see Production workflow and
Forking tutorial). Afterwards, run Autoreconf to generate the
appropriate version number:
Finally, to make sure everything will be built, installed and checked
correctly run (after re-configuring, and re-building). To greatly speed up
the process, use multiple threads (8 in the example below, change it
This command will create a distribution file (ending with .tar.gz)
and try to compile it in the most general cases, then it will run the tests
on what it has built in its own mini-environment. If
distcheck finishes successfully, then you are safe to send your changes to
us to implement or for your own purposes. See Production workflow and
Read in other formats.
GNU Astronomy Utilities 0.4 manual, September 2017.