https://bugs.freedesktop.org/show_bug.cgi?id=64930
Joel Madero <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW CC| |[email protected], | |markus.mohrhard@googlemail. | |com --- Comment #3 from Joel Madero <[email protected]> --- It's not that we don't want to backport it, it's that I have no clue what patch fixed it and tracking down the patch is likely to be time consuming. With over a 1,000 bugs needing to be triaged, spending time tracking down patches is just not a good use of QA time. This being said, I will add the two spreadsheet experts, perhaps one of them know when it was fixed and can backport the patch. As for "fixing every bug in 3.6" the reason we don't do this is because of regressions. For a patch to be applied to a later release of a series (such as 3.6.7),it has to go through extra review and our developers are already incredibly stretched thin, having to review every patch against 4.1, 4.2 master, 4.0 and then 3.6 is just too much work. If the bug is critical, a patch will be back ported, but for normal bugs like this one, a patch isn't going to be backported unless specifically requested and when we know what the patch is (in this case we do not) Also, in the future, please do not set a bug as REOPENED - this is for when a bug is assigned to developers only. This bug should be set as NEW (confirmed) or UNCONFIRMED (in the case of a bug not being confirmed). REOPENED means that the bug is assigned to someone, has been called fixed but then a user says the fix did not work - then it is set to REOPENED. Apologies that this particular bug has caught you, I really strongly recommend trying version 4 out, it's quite stable and has a lot of extra patches/features. @Kohei/Markus - any idea where the patch is for this one? I don't want you guys to waste time tracking it down unless you think it's vital for some reason, just curious if you know off the top of your collective heads. If not I recommend marking as WFM again as this is our general workflow in this case. -- 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
