On 1-9-2013 6:14, Martin Owens wrote:
On Sat, 2013-08-31 at 22:12 +0200, Johan Engelen wrote:
For this particular example of the pdf+tex output change, I would have much preferred a commit to trunk, then a mail to the devlist asking for a quick check, etc.
If you're not getting emails for merge requests, that could be fixed. I get them and they're very handy for knowing when code is ready.
There is too much Launchpad mailflow. Sometimes I do see the merge requests. But because they involve too much effort anyway, I mostly ignore it.
To branch or not to branch is a quandary, I've committed to trunk and liked the results, I've also committed and wished I could undo it.
??
This PDF work is a good candidate for a branch, anything with a likely or guaranteed multiple commits or possible shared collaboration on a block of work should be branched for sanity.
I disagree. For me, branches actually also prohibit easy-entry collaboration.
The branch merge request process is just a tool, we can use it or not use it. But we can't really expect people to commit to trunk and then email to get a code review... that strikes me as tool avoidance. Are you not using the lp tools because you don't know how yet? I could help if you want.
Yes, I avoid using bzr too much, because time.
-Johan