Comment 1 for bug 440011

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Graham Binns wrote:
> Public bug reported:
>
> What happens:
> Say you're working on a branch that is large enough to demand its own merge proposal (say, 800 lines) but which can't land until some subsequent work is done (for example because it was part of a much larger branch which must be landed all at once). The original M-P is reviewed and approved. As a result, the branch which can't land until the subsequent branch is completed will sit on the +activereviews queue until the subsequent branches (and so the original branch) land.
>
> What should happen:
> There should be a way to mark a merge proposal as "Approved but blocked" so that it doesn't show up as ready for merge on +activereviews.

We plan to add support for "prerequisite branches". Indicating in the
UI when a branch is approved but its prerequisite is not would make sense.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrEyTUACgkQ0F+nu1YWqI3gnQCePtxICUMm/jxi8gyFyFWV3xHk
oIUAninh6XbfLM+O9dC01wXOKLxTWwKD
=mAUL
-----END PGP SIGNATURE-----