change in fix-committed practice?

[Robert Collins]

Should we change how we use fix committed/fix released?

Currently we do: 'committed if its in our branch, released when its in
trunk'

But with 2.0 being a long lived target, separate from 3.0 or whatever,
being in trunk won't be 'fixed' for any bug that we're planning to
backport.

So I'm wondering what will work best to manage this. Do we assume that i
its not nominated it's not to be backported?

I'd be inclined to have fix committed/fix released keep meaning what
they mean and focus on separate tasks for 2.0 backports.

e.g. target to 2.0, then immediately set to fix committed in that task
if its fix released || fix committed in trunk.

-Rob

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090826/41060589/attachment-0001.pgp