On Fri 12 Mar 2010 14:11 -0600, Aaron Griffin wrote: > On Fri, Mar 12, 2010 at 2:12 PM, Loui Chang <louipc.ist@xxxxxxxxx> wrote: > > On Fri 12 Mar 2010 13:28 -0600, Dan McGee wrote: > >> On Fri, Mar 12, 2010 at 1:17 PM, Heiko Baums <lists@xxxxxxxxxxxxxxx> wrote: > >> > But just closing a bug should not be done. There's usually a reason why > >> > a bug is reported even if it's invalid. > >> > >> Seriously, present some examples here, this talking in the abstract is > >> stupid. We're all grown ups, no one is going to have their feelings > >> hurt. Without them I'm sick of the back and forth on this- most devs > >> leave bugs open for more than long enough to get feedback (and don't > >> get it!), and we would all rather have bugs be either fixed or closed > >> than hang around forever. > > > > I think another problem is that the bug wranglers aren't necessarily > > involved in development and don't communicate with the developers before > > taking action on a bug. That's no fault of the developer, but is a fault > > with the bug wrangler. > > Err? This sounds like quite a broad generalization without specific > examples. Do *you* have any examples you'd like to share? Sure. On occasion Paul Mattal will close or edit bugs in the AUR bug tracker. He's no longer involved in development and hasn't communicated with me about any of the tickets he touches.
