On Tue, May 12, 2015 at 7:51 PM, Scott Robison <sc...@casaderobison.com> wrote: > > None of these are impossible obstacles to overcome, but taken together as > a whole they do mean there is a significant amount of work to be done to > ensure policies are enforced, because the first time a policy is not > enforced for any reason at all, people will cry bug. From that point of > view I can appreciate why people are hesitant to try to implement something > like this. >
Ultimately, any restrictions are really only going to be "advisory". A determined dev could work around them. But, if you can't trust your devs to not intentionally subvert your processes then how can you trust them to develop your software? On the other hand, if government regulations require such strict controls, a DVCS, whether Fossil, Git or other, is likely not the tool you need. That's not to say that individual devs can't use Fossil on their PCs, only that *official* commits be made to the Central VCS. (I am also not saying a system like Perforce or Integrity is required. A well designed and properly implemented and tested set of hook scripts would likely provide what you need using SVN.)
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
