launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #06035
Re: lp-propose can make your life (and your reviewer's) better
-
To:
Martin Pool <mbp@xxxxxxxxxxxxx>
-
From:
Aaron Bentley <aaron@xxxxxxxxxxxxx>
-
Date:
Wed, 15 Dec 2010 21:56:32 -0500
-
Cc:
Launchpad Community Development Team <launchpad-dev@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<AANLkTi=gW27EL-7vAK68V7cgcJ1agy=6BdwXf0KK1TUy@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10-12-15 08:18 PM, Martin Pool wrote:
> The biggest thing I hit in using lp-propose was that it failed if
> there was already a proposal from the same branch
Please file a bug. It should only fail if the existing proposal is in a
non-terminal state, like "work-in-progress" or "needs review". And even
then, we could support a --resubmit that worked like the web UI's resubmit.
>, and for some things
> like 'doc' I tend to reuse the branches. But I guess I could just fix
> that.
The behaviour you describe is a bug, but there are many others like it.
Launchpad assumes feature branches all over the place in its design
(e.g. linking bugs to branches), and behaves badly when branches are reused.
I used to re-use branches, (remember bzr.ab?) but with Launchpad, you're
just fighting against the design when you do that. So you may wish to
reconsider that practice.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0Jf+AACgkQ0F+nu1YWqI3kfQCeLGnB8qLAGEs4IBtr/2H8QXLy
U4UAn3ETWqZEHbDHKbcNYnzxSNy/71L9
=HfTx
-----END PGP SIGNATURE-----
Follow ups
References