https://bugs.freedesktop.org/show_bug.cgi?id=56035
--- Comment #50 from Jorendc <jore...@libreoffice.org> --- Please don't take my comments personally: (In reply to comment #47) > 4.0.6 is considered as a final version. Is it really ok, to leave a final > version with a long known and rather critical bug? Yes it is, we don't support 4.0.6 any longer, please see https://wiki.documentfoundation.org/ReleasePlan#4.0_release We can't release 100th's of versions of 4.0-branch. People higher in the meritocratic ranking made this release schedule, which makes perfectly sense. Code develops continuously. And to look 2 major versions back as "will my patch work on that version too?" is a waste of time for every developer. It is even hard to backport a fix due the major code changes in some areas. And as every Open Source project, developer/volunteer time is gold. If you really want this patch inside a 4.0.x version, please look at this page to build your own LibreOffice. Then you can pull the fix and build your own version (hey! it's open source, remember?): https://wiki.documentfoundation.org/Development/BuildingOnWindows (In reply to comment #49) > In almost all machines, I am responsable for, I use to use the latest stable > version. > In my personal machine I need "Duden Rechtschreibung", which can be adapted > to LO4.0 (not to 4.1) with workarounds. See : https://bugs.freedesktop.org/show_bug.cgi?id=59107#c9 Not going to start a discussion, I'm going to lose that because I'm not a developer, but it looks to me that it's Duden's choice not to support LibreOffice anymore due not fix the link to libraries... I don't see why 1 extension should mean that LibreOffice has to change the whole release schedule? > But my question is more general: > - All versions of 3.6 did not index... > - Lo 4.0 did not index up to 4.0.3... > - Now indexing works, but there is a severe performance-problem. > - For one and a half year LO had these problems, publishing two final > versions. There is not even a comment about the problem in the release notes. This has to be addressed (which is done correctly by creating a bug report) and has to be added manually (or marked as MAB, but I'm not sure it applies to the requirements to mark it as such). > - There is a solution for these problems. > > Is it good for OpenSource to leave users alone with very annoying problem? Sorry, I don't agree what you're saying... As mentioned before: we have a release plan, we can't change the whole schedule because of an extension that doesn't support LibreOffice any longer. Otherwise you probably could upgrade to 4.1.4 really that'll be released really soon, which fix this bug. PS: if you really would continue this discussion about our release schedule, please do at our mailing list: http://www.libreoffice.org/get-help/mailing-lists/ Kind regards, Joren -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
