On 12/05/15 21:31, Matt Welland wrote:
On Mon, May 11, 2015 at 2:17 PM, Warren Young <w...@etr-usa.com
<mailto:w...@etr-usa.com>> wrote:
On May 11, 2015, at 10:48 AM, Andy Goth <andrew.m.g...@gmail.com
<mailto:andrew.m.g...@gmail.com>> wrote:
>
> X group manages Y branch.
Didn’t we all learn how to share in kindergarten?
If it makes sense for multiple groups with disparate interests to
all be working on a single common code base, with each group on a
different branch, you can treat incorrect checkins through the
same means you would if someone in group Y started tying up a
network printer in department X with constant printouts.
I’m saying you may have a people problem, rather than a technical
problem. This is a matter for management, not IT.
Different strokes for different folks I guess. Does your team use Unix
file permissions to prevent people from viewing files they have no
right to be looking at?
In my experience there are many times where a few judiciously applied
controls make *everyone* happier. The free-for-all model can result in
a cognitive burden if I have to expend mental energy worrying that I'm
committing to the wrong branch. A system that prevents me from making
a mistake can be an asset. The key of course is to not over do it. A
system with multiple layers of control can kill productivity also. For
many projects there is probably a sweet spot not at either end of the
spectrum.
If it's just for help preventing committing to the wrong branch, then I
guess a prompt asking you are you sure you want to continue y/N, would
be easier to implement that prohibiting a commit.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
