https://bugs.kde.org/show_bug.cgi?id=482519
--- Comment #16 from jimbo <loudsq...@tutanota.com> --- It's bad enough that you didn't test properly and pushed out an update that removes an essential part of the program, but the sheer lack of concern that it even occurred is sickening. The fastest and easiest way to fix a bug is to get on it immediately and assign the person who created the regression to fix it. It's clear that you didn't test properly, so it was up to us to write the bug report and it was done in a timely manner. Now it's months old and it's going to take even longer to undo the bug because the person who created it has long forgotten about it and moved on to more 'important' code. Here's something to think about, if a developer pushes an update and it's confirmed to break existing functionality, then that update gets rolled back until the developer in charge of the update fixes the regression. Otherwise the update never gets added. Whoever caused this should not be allowed to work on anything else until this is fixed, but that would require someone in charge and it's becoming painfully clear that no-one here is. -- You are receiving this mail because: You are watching all bug changes.
