Preventing avoidable accumulation of cruft is a highly useful feature and I don't mind if it takes some tuning to get the right behavior in Launchpad or if particular changes are made that turn out to have unexpected impacts. But please do reverse the janitor's actions on Bazaar bugs, because it has closed some bugs that should not have been closed. I don't want our developers to have to reverse them all by hand, or for good bug data to be lost. Closing valid bugs is much worse than leaving dead bugs open. > We did tell them ahead of time I don't remember getting any specific warning that this was going to happen, I might well have just missed it but I can't find it in my mail archive now. I do think it would be a good practice, before making bulk changes, to warn people and give them a chance to object. As far as I know there was no emergency situation that required this be done so (apparently) suddenly. > If the bug report is good, it should move rapidly to Confirmed. It's not > meant to stay in the Incomplete status; other uses of Incomplete are > incorrect (and I'll write a doc about this early Monday to clarify). I'm ok with that being the recommended or even required process; it's just the sudden enforcement that's bad. Bazaar developers had previously, and I think reasonably, been using 'needs info' when it needs information or discussion from a developer, so we didn't expect them to be suddenly closed. Suppose you came in Monday and Bazaar had suddenly archived all your branches with no commits for the last two months. It may be true that if you haven't finished your work in two months you may never finish it, but it would still be a surprising and worrying thing for the tool to do. -- Martin
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)