On Tue, Oct 6, 2009 at 2:24 PM, Barry Warsaw <[email protected]> wrote:
> On Oct 6, 2009, at 8:01 AM, Jonathan Lange wrote:
>
>> Branches have a list of connected objects that must be consulted
>> before deleting the branch. Some of these objects can be deleted
>> automatically when we delete the branch (e.g. bug links) and thus all
>> we do is confirm that the user really wants to delete those links.
>> Others cannot be deleted automatically (I can't think of an example).
>> In these cases, we block deletion until the user somehow breaks the
>> link between the branch and the non-deletable object.
>>
>> I think that the code & the UI should be re-used elsewhere.
>
> What about adding the ability to retarget those artifacts?  It doesn't
> happen often but almost every time I find myself wanting to delete a branch
> it's because I've created another branch to replace it.
>

Perhaps. I think that being able to delete things is a good first step though :)

> Maybe it doesn't make sense to move all artifacts (e.g. merge proposals)
> though.
>

Yeah, there's a fair amount of complexity here.

jml

_______________________________________________
Mailing list: https://launchpad.net/~launchpad-dev
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~launchpad-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to