On 22 Apr 15:38, Steve Schow wrote: > 3 - whether to use auto-sync or not.
I think you are making things overly complicated in question 3. If I understand properly, you want one trusted person to approve code before it gets into trunk on the main repository. Here is a policy that could accomplish that. Everyone works on separate repositories. When someone wants to put something in the main repository, he or she contacts the person who can write to the main repository, noting the branch, tag, or checkin. When that person approves of a change, he or she pulls from the appropriate repository and pushes to the main repository. The contact could occur inside tickets in the main repository, if you like. This is, in fact, the exact same workflow I would use with git. I don't see the connection to auto-sync. It is quite difficult it is to delete information from a fossil repository, so I don't think you have to trust your developers as much as you would with a git repository. Because of that, you might be able to come up with a less cumbersome workflow, such as the one that Richard alluded to. I'm not very good at fossil yet either, so I don't have thoughts on the other questions. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
