Merge lp:~gz/hydrazine/hide_unmerged_prerequisites_703057 into lp:hydrazine
Status: | Merged |
---|---|
Approved by: | Martin Pool |
Approved revision: | 93 |
Merged at revision: | 96 |
Proposed branch: | lp:~gz/hydrazine/hide_unmerged_prerequisites_703057 |
Merge into: | lp:hydrazine |
Diff against target: |
54 lines (+25/-5) 1 file modified
feed-pqm (+25/-5) |
To merge this branch: | bzr merge lp:~gz/hydrazine/hide_unmerged_prerequisites_703057 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
John A Meinel | Approve | ||
Review via email: mp+78736@code.launchpad.net |
Description of the change
Stops presenting approved merge proposals to be sent for landing if they have prerequisite branches that have not yet been merged.
For instance, currently this simple branch looks like it's ready to be landed:
<https:/
But in fact depends on a much bigger branch that has yet to be reviewed:
<https:/
Perhaps some kind of override should be added as well? I've occasionally in the past sent a branch to land immediately followed by another one that depended on it. However, it's probably better in general to actually see if the first one succeeds first, and with 30 minute run time these days that's less of a hassle to do.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/8/2011 11:44 PM, Martin Packman wrote: /bugs.launchpad .net/hydrazine/ +bug/703057 /code.launchpad .net/~gz/ hydrazine/ hide_unmerged_ prerequisites_ 703057/ +merge/ 78736 /code.launchpad .net/~jameinel/ bzr/2.1- categorize- requests- 819604/ +merge/ 78708> /code.launchpad .net/~jameinel/ bzr/2.1- client- reconnect- 819604/ +merge/ 78597>
> Martin Packman has proposed merging
> lp:~gz/hydrazine/hide_unmerged_prerequisites_703057 into
> lp:hydrazine.
>
> Requested reviews: hydrazine-core (hydrazine-core) Related bugs:
> Bug #703057 in Hydrazine: "feed-pqm suggests approved mp's with
> unapproved prerequisites"
> https:/
>
> For more details, see:
> https:/
>
> Stops presenting approved merge proposals to be sent for landing
> if they have prerequisite branches that have not yet been merged.
>
> For instance, currently this simple branch looks like it's ready to
> be landed:
>
> <https:/
>
> But in fact depends on a much bigger branch that has yet to be
> reviewed:
>
> <https:/
>
> Perhaps some kind of override should be added as well? I've
> occasionally in the past sent a branch to land immediately followed
> by another one that depended on it. However, it's probably better
> in general to actually see if the first one succeeds first, and
> with 30 minute run time these days that's less of a hassle to do.
I think this is reasonable.
review: approve
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
Q1PcACgkQJdeBCY SNAAN12ACgo1d0w YjI7Q9JjKoVmFAM J+lf LgZYXuHt2bYx70a 8B
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAk6
3XwAn3uLUdtOEeI
=s/g8
-----END PGP SIGNATURE-----