Martin, I don't agree to some of your points. Maybe you're speaking about lightweight checkouts, in this case I agree to some more.
Martin Owens-2 wrote
a. Checkouts prevent you from committing while offline
Not true: bzr commit -local -m "..." In this case, when you'll commit, your local versions are turned into a parallel branch (after you merge, of course). This point is true for lightweight checkouts.
Martin Owens-2 wrote
b. Urges the developer use a workflow which is not ideal for multi-participant development (i.e. what your seeing)
Ok, so please answer my previous question: what are checkouts for? @Krzysztof: do you agree with Martin? Why did you suggest using a checkout?
Martin Owens-2 wrote
c. Encourages less care to be taken when committing (this also applies to pushing directly to trunk, but at least there's one more command to type)
Don't understand this: which "one more command"? Maybe true for lightweight checkouts.
Martin Owens-2 wrote
d. We might adopt the review-then-merge process and this will leave some developers completely baffled as they'll no longer have trunk commit access.
This process would still be compatible with checkouts: eventually you need to have a place where to commit to and you may work into a checkout of that place being it the "real" trunk or simply a gate. Or are you talking about sending patches only?
Martin Owens-2 wrote
Use a branch of trunk (shallow even) and merge your changes into it.
Ok, this is a different solution I was trying to avoid because it has many disadvantages for small projects. I don't understand what you mean with "shallow even".
Martin Owens-2 wrote
`bzr uncommit` is great for backing out your modifications and reapplying them.
I completely disagree. In my opinion "uncommit" is evil if you are working with someone else. You may consider it _only_ if you are working alone and still can lead to disasters when abused.
Luca
-- View this message in context: http://inkscape.13.x6.nabble.com/Help-with-bzr-tp4969689p4969742.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.