launchpad-dev team mailing list archive

[Curtis Hovey <curtis.hovey@xxxxxxxxxxxxx>]

I am think about the kinds of activities that can be done to close as
many bugs as possible for the Launchpad 10.12 release.

I review all the bugs in the registry, answers, blueprints, and web
every month. I do not expect any to find many closed or duplicate bugs.
I tried searching other launchpad projects for overlapping issues, such
as gpg and ssh keys, but there were only a handful of dupes.

There are other ways to close bugs.

Fix trivial bugs
By trivial, I mean the fix can be put into review in 1 hour. For the
purpose of the bugjam, the time might be 2 or 3 hours. The essential
point is that the work is time-boxed, and that a contributor can do more
than 1 bug a day. The registry team has a zero-trivial policy so there
are rarely any such bugs for us to work on. We can fix trivial bugs in
other Launchpad apps.

Remove blocking issues
There are several bugs that are could be easy to fix if a blocking issue
was addressed. The team and user pages have could be redesigned to make
the remaining ui bugs trivial, or at least simple.

Reclassify the issue reported
Our policy is to accept any bug that we are will to accept a patch for.
We might be able to combine several bugs if we describe the kind of fix
we will accept. For example. There are many bugs about presenting,
editing, and deleting comments in several areas of Launchpad. I know
that all comments are IMessage. I personally would not accept a fix that
does not directly address IMessage; One fix for bugs, questions, and
merge proposals.

Reconsider a feature
Team polls are in a bad state. We could fix about 10 bugs in a week by
redesigning how polls are setup. We could also remove team polls and
close all the bugs.

Pay down tech-debt
There are many tech-debt tagged bugs that are refactorings. They are not
trivial, but they also do not require a lot of QA to confirm the issue
is addressed. Many issues are about removing code duplication, remove
unused code, or provide a test for code. I think many issues could be
fixed in 3 hours.

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

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