Trygve Laugstøl wrote:
You still read the issues, don't you?
Yes, just like I read Apache Maven issues which are already delivered via a separate list.
Tapping "read" for the couple of issues that might not relate to your plugin is to me less of a hassle than having developers that ignore the issue list.
Do you really expect that less developers will follow the issues if we split the lists? I mean, if somebody wants to ignore the issues, he can already do this now, just setup a nice filter and you're done. Admittedly, not subscribing to issues@ would be easier than defining the filter but it's still the same order of complexity, i.e. trivial. So personally I don't expect any change.
Because then they're only going to subscribe to the list without all the "noise" and risk loosing *critical* information about bugs in their plugin.
As said before, I believe developers that care will subscribe to both lists. Besides, it appears questionable practice to me to try to enforce people to read the issues by pumping them through [EMAIL PROTECTED] I might just got you wrong but IMHO this looks like a pessimistic view where we developers are assumed to be bad uncaring citizens.
Really, what mails people *effectively* read is a personal decision and shouldn't be guided by technical means. Just my two cents.
Benjamin --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
