Instructions and conventions for people wanting to work on librsync. Please consider these guidelines even if you're doing your own fork.
Fixes or improvements in pull requests are welcome. Please:
NEWS.mdto say what you changed.
tests/that passes or fails, and is hooked into
NEWS.md contains a list of user-visible changes in the library between releases version. This includes changes to the way it's packaged, bug fixes, portability notes, changes to the API, and so on.
Add and update items under a "Changes in X.Y.Z" heading at the top of the file. Do this as you go along, so that we don't need to work out what happened when it's time for a release.
Please try to update docs and tests in parallel with code changes.
If you are making a new tarball release of librsync, follow this checklist:
CMakeLists.txt- version is correct.
librsync.spec- make sure version and URL are right.
make all doc checkin a clean checkout of the release tag.
Test results for builds of public github branches are at https://travis-ci.org/librsync/librsync.