IMO: I'm more favorable of each fix on stable->same fix on trunk... so each one cleans after his own mess :-) than later having a single person dealing with merge problems.
Well... my other personality thinks there is one advantage about merging in batches... you only merge code after releases.. what means.. less chance of making mistakes.
Anyway... I just wanted to start the discussion.
I agree with your first personality - each person should make sure their changes are committed on both branches.
Actually this is what I have already done.
Also - and this critical - *please, please* make sure the merge history is updated when you do a merge:
I notice that not everyone is doing this! You know who you are :)
If you don't update this page it just screws it for the next person when they come to do a merge and end up re-merging the same stuff.