Many apologies to the devs generally and the individual one in question

users
#1

Hi :slight_smile:
I'd just like to extend my deepest regrets and apologies to the dev who had
worked on whatever it was that caused a breakage. I'm sure they felt
horrendous when they realised there was a problem! The highly public
thread must have been a nightmare! For that i am deeply sorry.

Our devs are great, fantastic even. The recent statistic showing how low
the error-rate is proved it. Working through coding must involve some
seriously intense focus and can't be easy! Errors happen and nothing is
perfect, of course but that is inevitable and unavoidable. It is pretty
awesome that this dev, and the others manage to get the error-rate so
incredibly low

This particular dev was doing really great work for a good cause and for
that we owe him or her a huge debt of gratitude.

Many, many thanks to all of them, and particularly to the one we have made
such a fuss about. Without their amazing work we wouldn't be here, arguing
about relatively tiny issues. Great job all!! :)))
Many regards from
Tom :slight_smile:

#2

Absolutely. I couldn't agree more.

Any previous comments in my post about the dev in question admitting
guilt should have been clarified more. I did say it was not a major
thing to be guilty of, and I really mean that. These things happen, and
a simple "oops, my bad, I'll fix that" is really all that I feel is
needed here. The great work the devs are doing overall is far, far more
important than any little slips (and even the odd major one) that may
creep in from time to time.

I really would like to be among the first to congratulate the whole LO
team on a job well done. I know my most seen thoughts on this list are
pointing out the bad, as that is where the room for improvement lies,
and I do try to be constructive, but that isn't enough. I should be just
as vocal about the good as the bad. And I do seriously believe the good
outweighs the bad.

A large congratulations to the whole LO team and the community here,
which does far more good than harm, despite the odd contentious thread.

Paul

#3

I did say it was not a major thing to be guilty of, and I really mean
that. These things happen, and a simple "oops, my bad, I'll fix that"
is really all that I feel is needed here.

I agree - but they didn't. Instead, users are told they need to 'pony
up' with $4,000+ to get their 'pet bug' fixed, rather than cry about it.

This is perfectly acceptable for pre-existing/old/legacy bugs and/or new
feature/enhancement requests.

The great work the devs are doing overall is far, far more important
than any little slips (and even the odd major one) that may creep in
from time to time.

In fact I agree very much. Hey - bugs happen, and I absolutely would
never accuse any developer of deliberately introducing bugs (although, I
guess, in some rare cases, it can happen)... BUT...

When bugs are discovered in new code added by a current/specific
developer, those bugs, when reported and confirmed, should simply be
fixed, by the developer that wrote the code, maybe <gasp> even with a
'thanks for the bug report'!

I just really wish that some developers would realize that the
(admittedly often valid) open-source retort of 'well, fix it yerself or
hire someone to do it' simply isn't an appropriate response, especially
for a bug in a 'new' feature that replaced a pre-existing feature that
worked perfectly for over 10 years - not to mention the fact that paying
$4,000 per bug to get them fixed simply isn't an option for some people.