Jenkins -> Travis CI
This development style has been adopted by the [[Contributors|ImageJ team]], with two additions (making the fall-out step much smaller):
* tests are added as automated regression tests (to be run by the [[
Jenkins|continuous integration]] whenever new changes were pushed) whenever possible.
* merges are usually done with ''--no-ff'', so that even fast-forwarding branches (i.e. rebased on top of ''master'') will get a merge commit in which the branch is described more broadly.