Continuous improvement for Yapsy
We really can't speak of kaizen for such a small project that only develops from by small strokes twice a year, but to take into account users' feedback I've started trying new tools to improve Yapsy's quality and make interactions with users a little smoother:
- for a few months now, the sources (originally in a mercurial repository on sourceforge) have been maintained in sync with a github repository. This should simplify the process of improvement proposals from the contributors, many of whom seem to like github a lot and will now be able to do pull requests.
- since the latest release, yapsy is also linked to the continuous integration service Travis CI so that each new commit triggers a full run of all unit-tests.
Now for those that may be interested the following are my impressions about these tools.