On 04/08/17 10:55 , Richard Haselgrove wrote: > I think those last two messages expose the nub of the confusion. Are > we, or are we not
Yep. > using Git in the way that Git was designed to be used? Git is just a tool, not a process. It wasn't designed to be used in one specific way. It makes possible and facilitates new improved ways to do software configuration management. Once you settle on your tailored process (hopefully based on widely accepted best practices) you implement it as a workflow - git then lets you carry it out effectively and efficiently. > Oliver, have you reviewed the release management paper that David has > just linked? Yes. I agree with some parts and I disagree with some parts. Fortunately it's likely to be revised soon. I *described the reasons* why the process needs to change a number of times on this channel and, sorry, I'm getting tired of repeating myself over and over again. Just see the 2-3 keywords threads to get an idea. Some of the reasons can also be read here: https://github.com/BOINC/boinc/issues/1874 Cheers, Oliver
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
