Question: Will 7.0 adress the issue of the "spinning Raptor"?

[adeine]

Well, it works both ways. Where such comments are warranted, yes, I agree there is little point.

[Ragnos28]

I, for one, appreciate the links to the Technical support forum you have provided. I'm having a hard time using the search function, to include results just for the Tech forum, or maybe is user error on my part.
I will bookmark your reply and check on them from time to time, especially if the fixes for the issue I've showcased will not be mentioned in the 7.0 fixes list.

[flywlyx]

We're not talking about any particular issue, though, but specifically about jolt related issues as experienced by the OP. On which front yes, there has been radio silence since the early days of 6.0, to the point where I can't remember any sort of official acknowledgement after release that a) this is an ongoing issue, and b) there are plans to address it further.

It's possible I've just missed all these responses (I can't read every single post on the forums, but I do skim), but here's a short list to the best of my knowledge along with their outcome:
...
I can't speak to what is happening behind the scenes, but 'radio silence' is an apt descriptor from the community perspective.

Do you use a bug tracker or compile these reports independently?
It would be quite convenient to determine whether a bug has been reported if there's a method to compile information like this.

[linolafett]

Please keep in mind, that if a bug was fixed after the release of the 6.20 build, it will only be available in the next build after this which is not yet released.
This is exactly the case for the highlighted reports #1526, #1645, #1637.
These were added to the bug tracker after the release of 6.20 and therefore any fixes (if they are fixed) will appear in the future.

[adeine]

I just wanted to say, thanks for looking into this linolafett. icy0's status update certainly makes me more excited to try 7.0, as I'm sure it will many others.

Here's to hoping the issues with Jolt can finally be put to rest.

[flywlyx]

This is exactly the case for the highlighted reports #1526, #1645, #1637.

Is there a known bug tracker where one could identify similar bugs?
It will benefit everyone involved in the bug reporting process.