On Jul 25, 2011, at 20:26 , Russ Paielli wrote: > I am wondering how good Fossil is for code review on a large project. (I am > a Fossil user, but I am currently only using it in the most basic way, for > my own project with no collaboration.)
Fossil has no specialized facilities for code review (there's even no way to comment a single checkin, other than commit message). Furthermore the default build still lacks hooks, which prohibits building any smart code review enforcement over it. If you don't need anything that advanced, it's quite OK. You can add/remove tags after committing. As a branch is a propagating tag, you can get something into/outside the working branch (see http://fossil-scm.org/index.html/timeline?r=Mistake for an example usage in a real repo). This way you can put a stamp on reviewed code/reject bad code/whatever your workflow wants. If you don't shudder on that kind of idea, you can event put review comments in commit message. Finally, knowing a tiny part of Fossil internals, I think that adding review facilities to the core would not be extremely hard. But someone would need to propose something good ;) Kind regards, Remigiusz Modrzejewski _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
