2009/8/10 Tim Penhey <email address hidden>:
> I was thinking about this exact think for the personal review page. For a
> personal one I'd tend to put the approved merges at the top because they
> should really be actioned as soon as possible (approved code that sits
> unmerged is a liability).
>
> Do you think that this would fit for projects too?
I think that would fit well - if they're the most important thing for
a person they're the most important thing for a team too.
Making them consistent makes it easier to understand how they relate.
For a team there's also the slight complication that there are some
things on which you personally can't take any action.
For the moment combining the pages is the best next step I can think of.
2009/8/10 Tim Penhey <email address hidden>:
> I was thinking about this exact think for the personal review page. For a
> personal one I'd tend to put the approved merges at the top because they
> should really be actioned as soon as possible (approved code that sits
> unmerged is a liability).
>
> Do you think that this would fit for projects too?
I think that would fit well - if they're the most important thing for
a person they're the most important thing for a team too.
Making them consistent makes it easier to understand how they relate.
For a team there's also the slight complication that there are some
things on which you personally can't take any action.
For the moment combining the pages is the best next step I can think of.
-- launchpad. net/~mbp/>
Martin <http://