change in fix-committed practice?

[Martin Pool]

I have one more suggestion for handling changes to 2.0, both before
and after the 2.0final release.

If you're fixing a bug, it should by default be based off the 2.0
branch and landing into 2.0 in the first place.  Therefore, propose
the merge only into 2.0.  We'll regularly merge from 2.0 into trunk
and this merge can be implicit.  There should be no need to make two
merge proposals in most cases.

-- 
Martin <http://launchpad.net/~mbp/>