Rich Bowen wrote: > There's also apparently a feeling that if you commit something to a > branch, and it doesn't end up getting accepted into trunk, that it was > wasted effort. I don't know how to fix that, but I do know that the more > often you make branches, the less that feeling impacts anybody. Branches > are for experimentation, and there's nothing intrinsically bad about > discarding a branch. It should have been a learning experiment. But I > can understand feeling bummed out if you put your heart and soul into a > branch that then got discarded.
One way I would suggest avoiding this happening is to discuss your work somewhere before expecting that it's going to be accepted with open arms. You're a lot more likely to get traction on your branch ideas if you get other people to help you build it. Plus, with other people helping, your branch code should by necessity be better. There are a handful of branches in the repo that I had no idea were there, and still don't know what the purpose of them is. Also in the realm of branches, I wanted to stop by the topic of bug hunts. I think that we should not be using a single public-write branch for bug hunts. My concern with this is that changes are often poorly vetted before merging with trunk. For the same reason that changes in code convention formatting of a whole file obscure a subtle logic change within that file, it is even more difficult to review changes when multiple logical or functional changes overlap. I don't know the solution. I think I would rather patch and commit. Opponents of that idea typically argue that patches are never reviewed or committed, although I think that a bug hunt should imply the assurance that there will be committers specifically available for this purpose. Of course, the same ideas apply to this as to branches -- not every patch is going to get in, and you'd do better by not coding in a vacuum. Owen --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
