Normal
I know the developers are busy (as I mentioned above). I also pointed out that they are so busy since the system of reporting bugs weighs them and the end users down... but no need to take my word for it go to any other high profile many user open source system. Let me get what your trying to explain about the bug fixing process with MP straight: Your saying that the developers "do not have to waste much time with "trying to reproduce" something because of the lack of informations.". You go on to say that some "test team" has the responsibility to find all the crash level bugs. If the developers don't try to reproduce submitted bugs because there is not enough information (there always is not enough information with forums posts), and nothing is done unless the test team can discover/reproduce the bug (which they usually cannot since they cannot possibly have the same same machine state and hardware as all the end users) So why bother asking end users to submit crash reports then? I don't follow the logic it just does not make sense in the framework of any project management I am aware of.This above quote is completely ignoring both what I have said above, the evidence present in other open source projects, and demonstrates clear lack of understanding of what an automatic bug submission system is.Please, look into it before making rash comments about it and/or disregarding it.I don't disagree with you. But as a project leader you should be less interested in what you like, and at least a little bit more open to what might improve the MP system. Most of this whole unfortunate thread could have been avoided with a simple "good idea, we the core developers might talk it over and consider" and I and others would be happy. I don't understand the level of negativity coming at me for such a simple idea... its not even new or radical! I have to wonder what happens with other more outlandish ideas with the project.Going by the responses to the suggestion above, it really comes across that perhaps the MP developers are not aware of what a crash report system is at the basic level - so it would be hard to imagine serious consideration was done. It takes 10 minutes or less to do a really basic integration of the codeproject crashrpt project but I am certainly not using that as a complaint, merely an example. This is probably not the best out there for MP but an easy example with test code to point to.An excellent suggestion and by all means I certainly may and put some code where my mouth is at some point in the future. However for the immediate time I will leave the topic open as a improvement suggestion and see if the developer community is even the least bit open to the idea. So far the reaction is quite negative (and scary).
I know the developers are busy (as I mentioned above). I also pointed out that they are so busy since the system of reporting bugs weighs them and the end users down... but no need to take my word for it go to any other high profile many user open source system. Let me get what your trying to explain about the bug fixing process with MP straight: Your saying that the developers "do not have to waste much time with "trying to reproduce" something because of the lack of informations.". You go on to say that some "test team" has the responsibility to find all the crash level bugs. If the developers don't try to reproduce submitted bugs because there is not enough information (there always is not enough information with forums posts), and nothing is done unless the test team can discover/reproduce the bug (which they usually cannot since they cannot possibly have the same same machine state and hardware as all the end users) So why bother asking end users to submit crash reports then? I don't follow the logic it just does not make sense in the framework of any project management I am aware of.
This above quote is completely ignoring both what I have said above, the evidence present in other open source projects, and demonstrates clear lack of understanding of what an automatic bug submission system is.
Please, look into it before making rash comments about it and/or disregarding it.
I don't disagree with you. But as a project leader you should be less interested in what you like, and at least a little bit more open to what might improve the MP system. Most of this whole unfortunate thread could have been avoided with a simple "good idea, we the core developers might talk it over and consider" and I and others would be happy. I don't understand the level of negativity coming at me for such a simple idea... its not even new or radical! I have to wonder what happens with other more outlandish ideas with the project.
Going by the responses to the suggestion above, it really comes across that perhaps the MP developers are not aware of what a crash report system is at the basic level - so it would be hard to imagine serious consideration was done. It takes 10 minutes or less to do a really basic integration of the codeproject crashrpt project but I am certainly not using that as a complaint, merely an example. This is probably not the best out there for MP but an easy example with test code to point to.
An excellent suggestion and by all means I certainly may and put some code where my mouth is at some point in the future. However for the immediate time I will leave the topic open as a improvement suggestion and see if the developer community is even the least bit open to the idea. So far the reaction is quite negative (and scary).
