Ubuntu Bugzilla to Malone (Launchpad) migration complete

[Christian Robottom Reis]

On Mon, Jan 16, 2006 at 06:27:08PM +0000, Ian Jackson wrote:
> * Launchpad should not require me to periodically log in again.

This is a bug. I've had to do this occasionally -- for instance, today
when I arrived Launchpad had been upgraded, and I had to log in again.
Stuart, do you have any clue why this happens?

> * Bug text should be rendered in a fixed-width font.

This is an ongoing war. Matthew, what's the news from the front?

> * The inability to easily edit the bug URL to go to a different bug
>   is a significant useability reduction compared to Bugzilla and
>   Debian.  (This is something one does very very often.)

Do you mean the +bugs/ versus +bug/ issue, or is it because the bugs are
on different "branches" or the URL tree?

It might help you to know that

    launchpad.net/bugs/929

transports you to the correct page.

> * Rendering bugs (eg, in
>   https://launchpad.net/distros/ubuntu/+source/firefox/+bug/27783
>   the URL overflows the area intended for the bug text).

I have a fix for this (it's bug 929) that is going to be rolled out at
some point when I get it reviewed. Only issue holding it up on my side
is deciding what's the proper way to break the URL -- none of the
alternatives is perfect, but which is the least worse of them?

    https://launchpad.net/products/launchpad/+bug/929

> * The phrases `Fix Requested In' and `Request fix' seem meaningless to
>   me.  I'm scared to try out clicking on `Request fix' in case it does
>   something stupid.  Presumably these could be translated into
>   some more standard terminology ?

They might, but I don't think anyone has ever been able to come up with
a better set of terms with them. These links are what connects bugs to
tasks -- each bug can have one or more tasks, which are places that need
work done to fix the bug. When you have a bug reported in Ubuntu that
needs to be fixed upstream and then packaged, that means two tasks: an
upstream task (that may be linked to an upstream bug tracker if upstream
has specified one) and an Ubuntu task (that will probably be fixed after
the upstream bug is).

Having read the long version, do you have suggestions?
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125