<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">El 25/09/13 05:50, Daniel Letzeisen
escribió:<br>
</div>
<blockquote cite="mid:52425D91.7040601@gmail.com" type="cite"><br>
<blockquote type="cite">I am not 100% against it. But, in this
case, I would like to be able to unilaterally close the bug
invalid if the minimum required data is not there.
<br>
</blockquote>
Agreed. If an advanced user goes out of the way to file a bug
report directly not using the tools, s/he should have some
technical insight into the issue or it's a really obvious bug
(like a typo in a package description).
<br>
<br>
</blockquote>
I think marking it as 'incomplete' and asking the user for further
information is enough; since the bot 'Lauchpad Janitor' will clean
it automatically in 60 days, and there's no need for the user to
write a new report if he's interested in helping.<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">El 25/09/13 05:50, Daniel Letzeisen
escribió:<br>
</div>
<blockquote cite="mid:52425D91.7040601@gmail.com" type="cite">I'd
love it if every bug was tagged with an associated release(s), and
once all the releases were EOL, the bug would automatically become
Incomplete and Expire unless a user indicated it still affects
them in a current release. <br>
<br>
</blockquote>
Yes, a good solution will be perhaps a bot marking the report as
'incomplete' and saying:<br>
<blockquote>Please, if you are still experiencing this bug:<br>
- Change its status to 'confirmed' or 'triaged'<br>
- Tag it with the names of the Ubuntu releases where you find it
(<a class="moz-txt-link-freetext" href="https://wiki.ubuntu.com/Releases">https://wiki.ubuntu.com/Releases</a>)<br>
</blockquote>
Also will be a good idea the bot to complete the tag list of
'confirmed' bugs with the names of currently supported releases from
the release the bug has been notified to the latest tagged.<br>
<br>
<br>
</body>
</html>