| Thread Previous • Date Previous • Date Next • Thread Next |
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.
Maybe it doesn't make sense to move all artifacts (e.g. merge proposals) though.
I think we should further explore, how an "incomplete" status for projects would work, like Kiko suggested. Or call it the "incubation" phase (have heard that term used before). This would also address a similar need in project and license review which need not take place until after the project has left that phase.I think we actually need to completely overhaul the project registration process, with test registration being one of the factors to consider.
It's certainly a use case that we have not yet addressed directly. We've taken side shots at it (i.e. the staging exit), but taking a detailed look at this use case would be worthwhile.
-Barry
Attachment:
PGP.sig
Description: This is a digitally signed message part
| Thread Previous • Date Previous • Date Next • Thread Next |
