Problems linking bug w/ upstream

[Bjorn Tillenius]

On Fri, Nov 10, 2006 at 03:47:33PM -0600, kiko at async.com.br wrote:
> On Fri, Nov 10, 2006 at 08:47:48AM -0800, Bjorn Tillenius wrote:
> > > One alternative to this setup is to have a single entry point to adding
> > > new tasks, without the user deciding up-front whether it's a package or
> > > an upstream. That would allow us to provide more help text in the first
> > > page that could help answer this common question.
> > 
> > This would help, and there's a bug open on doing it,
> > https://launchpad.net/products/malone/+bug/1334.
> 
> Yeah. High pri?

At the moment it's not trivial to do, and considering I have quite a
lot of other important things to do, I'd rather leave it at medium
priority.

> > Another thing that would help is to have a meaningful error message. If
> > a product can't be found, we should explain what that means, and what
> > the user can do to correct it. This is bug
> > https://launchpad.net/products/malone/+bug/1922, btw.
> 
> And critical for this once?

Critical is probably fine for this one, since it only requires adding a
custom error message, which is quite easy to do.

Regards,

Bjorn