On 5/11/2015 11:57 AM, Richard Hipp wrote: > On 5/11/15, Andy Goth <andrew.m.g...@gmail.com> wrote: >> My wishlist derives from my organization's needs which are currently >> being met by ClearCase ... > > My "mechanism not policy" rule derives from some very bad experiences > with ClearCase...
I understand completely, and I sympathize. Nevertheless, we have projects where a single repository would contain branches and versions delivered to many different customers, including customers to whom inadvertent disclosure of things meant for other customers would have rather thorny consequences. It's not sufficient to trust that the engineers will never make mistakes or move tags around after having shipped. Of course it's possible (and a very good idea) to externally keep track of the SHA-1 artifact ID of various pertinent check-ins, e.g. in a version description document. But we engineers just want to be able to search for YF21UNAF-TEST-1.03 or whatever, without having to worry that somebody moved the label to sneak a spelling fix past QA. -- Andy Goth | <andrew.m.goth/at/gmail/dot/com>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
