https://bugs.kde.org/show_bug.cgi?id=470474
--- Comment #14 from k...@imkx.dev --- > I'm not really familiar with the process here so I apologize for asking the > obvious. Am I understanding correctly that now we're just waiting for it to > be merged, so (a future) update will fix it? No worries, you're not doing wrong for asking. You're pretty much right. You can imagine it as if there is the releases or versions, (5.27.1, 5.27.2...... etc.) and those are a combined effort to fix bugs, add features or clean up the code and so on. What goes into these versions is dependent on what's relevant at that time, it's just a continuous development process in which a lot of people and the community in general are involved. A fix for this bug has been developed and proposed as an addition to the next possible version. When that will be, I actually don't know myself. Someone has to approve the request first to make sure it's nothing malicious, has proper code style, quality and so on. One thing you could do, if you want to use the fix earlier than officially released, is build it yourself (from the branch the merge request, that I linked, resides on) after making sure it's nothing malicious. That's why open source is so helpful. -- You are receiving this mail because: You are watching all bug changes.
