> If the build breaks for an unrelated reason, you can lose a whole week of development to screwing around. This happens often on some projects at Google (although 2 days is the longest I've seen it broken). Others have…
Thanks for the info! > Piper has branches I've worked on two teams so far, neither of which used the branches you described. They opted to either flag off features or keep long-running CLs. However, I'll try to learn…
Coming from companies that use reasonably-sized git repos, I absolutely hated Google's VCS. Here's some of my painpoints with it: * No branches. If you want to make a temporary code branch, you create a CL (Google's…
> If the build breaks for an unrelated reason, you can lose a whole week of development to screwing around. This happens often on some projects at Google (although 2 days is the longest I've seen it broken). Others have…
Thanks for the info! > Piper has branches I've worked on two teams so far, neither of which used the branches you described. They opted to either flag off features or keep long-running CLs. However, I'll try to learn…
Coming from companies that use reasonably-sized git repos, I absolutely hated Google's VCS. Here's some of my painpoints with it: * No branches. If you want to make a temporary code branch, you create a CL (Google's…