Bernhard R Link <[EMAIL PROTECTED]> writes: > But it is a time that is well invested. If a maintainer does not look at > the bugs, he cannot give them due priority. Thus a maintainer needs to > look at them anyhow and do a fast assessment how important it is, how > much work it would involve to fix it or even what kind of tests or > considerations would be needed to make sure it is a bug at all. And if > it is done, a short answer can be made with the results of that.
Looking at a bug to decide whether I have to work on it right away takes me about thirty seconds. Replying to the submitter to explain why I'm not working on it right away and what my general reaction to the bug is takes a lot longer, plus it usually opens a further conversation. I'm happy to do that work when I have time, but they're not equivalent amounts of work. I read every bug report on any of my packages immediately, but I don't necessarily have the time right at the moment I see it to respond to it. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
