Hi :) This "blame the user" mentality belongs more properly in the MS and proprietary world. It makes more sense in the OpenSource world but generally i don't see it in other OpenSource projects (apart from Evolution) and i'm quite glad of that. It's one of the many reasons i'm glad to be mostly freed from the MS world.
Tanstaafl seems to be being blamed for at leat 2 contradictory things here. 1. for bringing up his pet bug too often 2. for not bringing it up often enough. Hmm, tricky. I thought bug-reports announced to all subscribed to that bug-report when a patch was released and again when the patch got into a main-branch. Regards from Tom :) On 2 October 2014 09:34, Charles-H. Schulz < [email protected]> wrote: > Le 01.10.2014 22:21, Tanstaafl a écrit : > >> On 10/1/2014 12:54 PM, Florian Reisinger <[email protected]> wrote: >> >>> 9 bugs for 30k €. That is a fair price... >>> >>> Continuing reading the thread now... >>> >>> PS: If a volunteer does not tackle your pet bug, you should get >>> someone to fix it (search for "libreoffice L3 support" for other >>> service provider... >>> >> >> Let's see... >> >> Pay you extortion in the amount of $4,200 (assuming I can get just one >> bug fixed for 1/9th the quoted price, which I suspect is unlikely) to >> fix a *regression* caused by someone arbitrarily deciding to *replace* >> (as opposed to providing the new feature, but allow users to fall back >> to the old functionality) a feature that has been working fine for 10? >> years with a 'new & improved' version (not knocking the feature itself, >> just that it doesn't work properly in that it lacks a very fundamental >> and necessary capability), or... >> > > > What you call extortion is a price of a service. I suspect your employer > does sell products or services too, and that you are yourself paid to > accomplish something, aren't you? > The real extortion here is someone who expects people to work for his own > needs for free. > > As for regressions, they are indeed arbitrary. They are obviously not > intended, and software development *works that way*. Don't belive me, just > go ahead, buy MS Office licenses, and wait for the next bug to happen. Then > you can come back here and tell us about bugs and regression. > > Note that the patch already exists, but that you were not proactive in > even calling attention on the issue. This seems to suggest that the > situation your company is on with respect to your LibreOffice deployment is > not really problematic. If you are not ready to pay anything to have > someone fix your problem, and don't even show up to call for an integration > of the patch as soon as possible, then it looks like your problem is not > really urgent, even in regard to your corporate requirements. > > >> Stick with 4.1.6 (that actually works). >> >> > It works really well, with an important vulnerability left unpatched. That > seems to be not important to you either: http://www.libreoffice.org/ > about-us/security/advisories/ > > I guess everyone has his or her own priorities, but if anything happens > because of that, you will have been warned. > > > Best, > > Charles. > > > > -- > To unsubscribe e-mail to: [email protected] > Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to- > unsubscribe/ > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/global/users/ > All messages sent to this list will be publicly archived and cannot be > deleted > -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
