If make daily commits, could them be dirty and buggy? I can't guarantee that I'll be able to produce completed parts of code every day.
Just use the common sense. If you work on an isolated feature for one day and it ends as almost finished, but you need a few hours to clean it up over the next day or two, you can certainly do the commit after two days, or even after three days. This is not a problem.
But if you work on some open long-running feature that will definitively take many days or even weeks to finish completely, don't batch the changes, but commit your progress frequently (say daily or once every two days). Dirty and buggy commits are fine if it is a work-in-progress and you plan to improve it eventually.
(If you are really pedantic about the software engineering process, you can even set up multiple feature branches to distinguish the two cases. But this is in no way a requirement from us.)
The point is to have an early indication that you are stuck on something or that something is not developing in the right direction. The greater the granularity of the commits is, the greater is the latency of this indication and the more time might be wasted.
M.D. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
