You might want to take a look at this: http://www.fogcreek.com/kiln/features/code-reviews.html
It's just something I stumbled across surfing the web. I have no idea how good it is or whether it makes any sense at all to add something like this to Fossil. --Russ P. On Tue, Jul 26, 2011 at 11:13 AM, Ron Wilson <[email protected]> wrote: > On Mon, Jul 25, 2011 at 2:26 PM, Russ Paielli <[email protected]> > 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.) > > If your developers are making commits to their own branches, then your > review process can selectively merge in the changes that are accepted. > > As Remigiusz mentioned, tags can be added to a commit to indicate > Accept/Reject status from the reviewers. If the consesus is to accept > the code, then your integrator can merge in the accepted changes. > Since tags can have a value, they can reference a document with a > detailed report from the reviewer. > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- http://RussP.us
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
