On Sat, Feb 25, 2012 at 09:17:57AM -0500, Richard Hipp wrote: > For contributing to Fossil itself, there is a Pre-checkin Checklist that > developers are suppose to follow prior to each 'fossil commit". (A > similar checklist exists for SQLite.) A key element of this checklist is > the "fossil diff" - to make sure you really know what you are about to > check in. Very often I spot debugging statements that should have been > removed, missing or erroneous comments, bad indentation, or goofy variable > names during that "fossil diff" step, and thus have an opportunity to > correct those errors prior to making them a part of the permanent record. > I also find that I am able to write better checkin comments if I have just > reviewed all changes associated with the checkin. I highly recommend that > you adopt some kind of short, simple pre-checkin checklist for your > projects as well, and that this checklist involve a "diff" of what is > about to be checked in. It really does help.
Is the 'pre-checkin checklist' for fossil and sqlite publicly documented somewhere? This sounds like a good development habit to get into and it would be nice to maybe have a template to start from. -- Christopher Berardi http://www.natoufa.com/ May grace and peace by yours in abundance. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
