<br><br><div class="gmail_quote">On Thu, Aug 26, 2010 at 8:13 PM, Andrew Flegg <span dir="ltr"><<a href="mailto:andrew@bleb.org">andrew@bleb.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Although one *could* have a different email address for bugs rather<br></div>
than general support.</devil's-advocate><br></blockquote><div><br></div><div>Yes, well, nitpicks :) The only problem with the field is that some people</div><div>tend to forget to modify the maintainer field, leaving upstream addresses.</div>
<div>This is also an error so we might as well solve two problems in one go.</div><div><br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
If there are some, and developers don't want to have the "hassle" of a<br>
big web based application, a blank "Bugtracker" should equate to<br>
<a href="http://maemo.org/packages/view/" target="_blank">http://maemo.org/packages/view/</a><package>(/<version>). That gets the<br>
testers the visibility of previously mentioned issues, which seems to<br>
be the main problem.<br>
</blockquote></div><div><br></div><div>I could go with that. That's no worse than a bugtracker put in just to</div><div>pass QA, so functionally, we're not losing anything.</div><div><br></div>