On Sat, 12 Jan 2013 19:31:26 -0500 Richard Hipp <[email protected]> wrote:
> I contend that this points up issues with your development process, not > with Fossil. If your developers do not notice that a fork has occurred for > days, then they are doing "heads down" programming. They are not > maintaining situational awareness. ( > http://en.wikipedia.org/wiki/Situation_awareness) They are fixating on > their own (small) problems and missing the big picture. This can lead > dissatisfied customers and/or quality problems. > If this is the case, I whould suggest better solution. Only 3..5 cases in a year are not enough to train the team enough and to increase the situation awareness of the people. Isn't it better to make fossil to fork randomly with probability, let say, 1:20. This approach will train the users very quick. They will acquire good habits and will never allow airplain crashes and medical errors because of situation awareness loss. -- John Found http://asm32.hopto.org _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
