Comment 2 for bug 406058

2009/7/29 Tim Penhey <email address hidden>:
> This is the entire use case for the "work in progress" status of a merge
> proposal.
>
> Perhaps what we need to do is to allow someone to create the proposal in a
> work in progress state but only send out the review email when it is set to
> "Needs review".

Ah, interesting. So the 'work in progress' represents an intended
future landing, perhaps far in the future.

I think I might want to look at the diff for someone else's branch
even if they haven't got around to declaring that thing... But
perhaps if it became part of the normal workflow and they always
existed that wouldn't be a problem.

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