On 3/31/2010 2:53 PM, Jeff Spaleta wrote:
> No one has so far defined a workflow that requires an accurate audit
> of active deficiencies in any release. Closing bugs fixed rawhide
> certainly cause some annoyances because closed bugs are marginally
> harder to search for (because you have to request closed bugs to
> search through) when encountering the problem again and subsequently
> cause bugs to be refiled unnecessarily. The same goes for any closure
> condition that bodhi doesn't automatically perform when an update gets
> pushed to stable.
>
> -jef
>
This is why I actually really enjoyed the brief period that bugzilla
automatically searched closed bugs, though I can see why that isn't
sustainable. Perhaps it could automatically search closed bugs for
supported releases?

- Orion
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

On Wed, Mar 31, 2010 at 6:35 PM, Orion Poplawski <orion@cora.nwra.com> wrote:
> This is why I actually really enjoyed the brief period that bugzilla
> automatically searched closed bugs, though I can see why that isn't
> sustainable. *Perhaps it could automatically search closed bugs for
> supported releases?

Or perhaps... its time to find the manpower to extend the "community"
web portal design for an end-user workflow that interacts with
bugzilla.

-jef
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel