https://bugs.documentfoundation.org/show_bug.cgi?id=95039
--- Comment #15 from Norbert Thiebaud <[email protected]> --- "Most of my clients are not willing to use software that exhibits hard crashes" Then your clients cannot possibly be using any software, and since you had open that bug for 'Windows' surely you statement is not true. Oh, btw, your 'clients' are not our 'clients'. We are a free software project. most of us are doing this on their free time, none of us have any obligation to care about your clients... There are services company that specialize in that, if you want a service-level agreement you should contact them. "I'll take a few minutes of my time to explain best practices regarding software testing and development." You should not have. keep your precious time and avoid wasting ours at the same time... "I am available for trainings on this topic," And yet you seems not to be very familiar with it as illustrated by you tantrum and demands. "It is very common in the industry for software to have major bugs that are not easily reproduced This is nothing new." No easily reproduced is not the same as not reproducible by any known method. "My report is a good example of one that provides extensive details as to the steps that resulted in the product (LibreOffice, in this case) crashing." your report boils down to: I managed to crash the product, I can't reproduce the crash, and I won't give you the document that trigger it.. iow, no dev can do anything about it. my favorite part is "2. LO Calc would open, the spreadsheet would display, the error would appear, and LO Calc would hard crash. There was no way to try to save the file." the error being the crash-notification dialog right ? that was not followed by Lo crashing 'hard' (as if there was such a s thing as a soft crash), that was preceded by it, which triggered the crash dialog. No way to save the file ? you said you just opened it, why would there be any reason to save anything.. beside yeah, upon a crash by definition you can't continue to use the app, to save or otherwise.... There is nothing inherently wrong with your attempt, and no-one would have pointed it out had you not insisted to be an expert on the topic and claimed to have provided: "Now that you have a quality report" If you _actually_ had any understanding is what is involved in software development you would not have hold such ludicrous assessment. "Such a team will also work to encourage users and developers alike to provide more supportive data." we did and we get: "I cannot upload the file." "I tried the jump list again to load the ORIGINAL file (the one that just repeatedly caused the hard abend), and it suddenly loaded without error." How on earth do you imagine anyone can do anything with that. "The onus is on the development team to gather more information about the bug, in order to fix it." You do not have the first clue about how free software works... the devs owe you nothing, nor does any other _volunteers_ working on the project. Most of us are usually willing to help, but banging your fist on the table with a sens of entitlement is not the best way to get people to spend their free time helping you. and btw, earlier you said: "You don't speak for this project, and thankfully, you never will." If you cared even a little about the project, you might have seen this page: https://www.documentfoundation.org/foundation/board/ pay attention to the third entry there... my advice: keep off the keyboard for a few days... collect yourself, try to reproduce the bug and come back, keeping in mind that we are not your vendor or employee.. we do that in our spare time and certainly not to be yelled at, insulted, patronized.... I, for one, do not hold grudge.. so I will assume, for now, that you just had a bad day, and needed to vent, and that normally you are not like that. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
