Launchpad logo and name.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index ][Thread Index ]

Re: Massive bug expiration spree (Restoring all bugs to their previous status)



On Mon, 2007-09-24 at 21:29 -0400, Curtis Hovey wrote:
...
> We plan to revise the bug expiration process in two ways. Firstly, we
> will warn users that incomplete bugs will be invalidated if action is
> not taken (https://bugs.edge.launchpad.net/malone/+bug/141604). Secondly
> we will revise the rules regard what qualifies a bug for expiration
> (https://bugs.edge.launchpad.net/malone/+bug/141597). 

Well that was cruel of me to paste URLs from one of the testing servers.
I'm sorry for the tease. The correct URLs are:

https://bugs.launchpad.net/malone/+bug/141604
Expiration janitor should put an expiration notice on bug page.

To make the process of expiring bugs more visible, bugs that are
scheduled for expiration in less than a week should have notices put up:

  /!\ This bug will be expired in 7 days if no further activity occurs
(_find out why_).



https://bugs.launchpad.net/malone/+bug/141597
bug janitor expires bug reports that should remain open.

Bug 80502 was expired even though it is a duplicate of another bug that
it is Confirmed. This doesn't seem like the right behavior to me.

Addendum
Five points have been brought up on IRC and mail that should be
addresses in this bug
1. Do not expire duplicates.
2. Do not expire reports with milestones.
3. Do not expire bug that have no comments.
4. Do not expire bugs if any affected area has a bug watch.
5. Use the date of the last comment to track activity, not the date when
the report became incomplete.


> We will perform a public test on staging with the revised expiration
> rules. Launchpad users can see the results, and provide additional
> feedback that we will incorporate into the rules. We will not run the
> bug expiration process in production until the community agrees the
> process is right.

I should also clarify that staging is a test environment where we run a
copy of production data with a development version of Launchpad. We can
use that environment to safely run the bug expiration process to view
the changes that would be made if it ran in production. We will make
arrangements to report what will change. Without your input we will make
additional changes to both the notice that runs before expiration, and
the rules that qualify a bug for expiration.

Sorry for the inconvenience.

-- 
__Curtis C. Hovey_________
http://launchpad.net/

Attachment: signature.asc
Description: This is a digitally signed message part



This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.

(Formatted by MHonArc.)