[Reminder Daemon] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage

[Flossy Cat]

https://bugs.kde.org/show_bug.cgi?id=481024

--- Comment #38 from Flossy Cat <flossy-cat at online.de> ---
(In reply to David Faure from comment #34)
> It is a bit contradictory to want to use a "stable LTS version" (which means
> no new features) and then ask for a new feature to be added to it. I know
> it's frustrating because that new feature is needed to fix a regression, but
> it *is* a new feature.

Your claims are counterfactual:
This bug report is about a regression and re-establishing functionality which
was present in previous versions since many years and were deprecated without
announcement and any consideration on the usability of Kontact for calendaring
afterwards.

"Regression" is part of the title and pervades both the bug report itself as
well as the discussion thread.

The patch you kindly provided – according your own words – reused code from
"korgac" (which was scraped without consideration of the impact, which is the
root cause of the regression), proving the regression.

As stated in comment 8, this change happened 2 years before my bug report and
similar bug reports like mine existed 6 months after this crippling change –
i.e. 18 months before my bug report. This should have been early enough to
avoid having a crippled Kontact (unusable for calendaring) make its way into
LTS and distributions like OpenSUSE and SLE.

The ignored users of these early bug reports probably have left the KDE user
base meanwhile.

I'd worked around 6 month till the advent of LEAP 16.6. I'd would have to wait
roughly a further year to see your patch in the regular distribution. (Or to
compile myself and lose automatic security patches or wade through the
dependency hell of OBS KDE Factory versions and lose other SW because of
resolver clashes – on several systems.) 

That is neither viable nor acceptable, and in any case much more effort than to
migrate to a new PIM solution.

-- 
You are receiving this mail because:
You are the assignee for the bug.