https://bugs.documentfoundation.org/show_bug.cgi?id=70883
--- Comment #18 from b. <newbie...@gmx.de> ---
@Buovjaga:
> If you think some report is wrongly closed as a duplicate, please explain why
> you think so.
no, i didn't say that, thus nothing to explain,
> Findings from duplicates can be copied as comments to the open reports.
i know that, and did so sometimes,
what i'd say was:
"(i like libreoffice and consider it one of the best office suites, the weakest
points are the 'old bugs', that nobody cares for them, and that new findings
are pulled away as duplicates. this is a general weakness of the development as
a community, and the systematics of the bugtracker.)"
as an extenuation of a - gallows humor - remark:
"and again i tapped on an old bug nobody cared for since years ... "
mean point, as bugs and bugtracker are actually handeled they lead developers
to the triage: 1. new bug? oh no, it's a duplicate, 2. care for the origin? oh
no, too many comments, difficult stuff, 3. what do do? mark as dup and care for
something else. and that buries 'old bugs'.
you can verify this opinion on this bug - 6 years, no patch, no progress, on
other fields like 'shared formulas', parallelizing, - there had been some
progress - macro functionality, iterations, comment slowdowns, autocalc, #REF!
errors and so on, or on #62196 mentioned by Mike - basic functionality, six
years, 13 duplicates, no patch, no progress, it already has a sibling #65606
with some duplicates, and a grandfather #34599 ... you'll see that bug handling
for old bugs in calc (and libreoffice?) is not the most effective point of the
project.
i wouldn't cry about that in 'bugs' - imho intended for work on the factual
problems - if i'd know any better place, perhaps you can give me a hint.
reg.
b.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
