Comment 6 for bug 1334

On 1-Feb-06, at 6:36 AM, Matthew Paul Thomas wrote:

> Public bug report changed:
> https://launchpad.net/malone/bugs/1334
>
> Comment:
> "At least if the bugtask is explicitly rejected a future bug reporter
> searching for their bug will be able to see in a single page that
> their
> bug exists in 4.10 but is fixed in 6.04, and so can consider
> upgrading."
>
> If someone using 4.10 is searching for a bug, they already know
> that it
> occurs in 4.10, so a 4.10 task isn't really necessary (except inasmuch
> as it reassures people that they have the right bug report). What I'm
> trying to avoid is people thinking they're being helpful by saying
> "hi,
> this also occurs in 4.10" (creating extra work in rejecting that
> task),
> when they don't actually want the bug fixed in 4.10, being quite happy
> to upgrade to 6.04 to get the fix instead.

FWIW, users should never be "requesting a fix"/reporting a bug/etc.
in a specific release. In the Malone model, release-specific always
means "backport/security fix", and we now have a backport-specific
UI. IMHO, the best UI for this is something like:

   <http://flickr.com/photos/84096161@N00/88275619/>

I think the layout of that page can be improved somewhat ($columns--,
among other things; I'm not really interested in a deep discussion of
the various aspects of this page outside what relates specifically to
this bug report), but I think the way it presents upstream status,
and reporting the bug elsewhere is pretty interesting.

What do you guys think?

Cheers,

--
Brad Bollenbach