The changelogs in minor releases are too vague. They mention new features but do not list bug fixes. Users cannot tell which reported problems were fixed. That is eroding my trust in Cursor.
Please:
Publish detailed release notes for every release. List bug fixes and link them to the relevant issues. VS Code and JetBrains do this well.
Dedicate a release to bug fixes and stability. Focus on long-standing bugs, regressions, and reliability.
…I want to keep using Cursor, but I also want to see bugs fixed and progress reported clearly.
Hi @ragnoroct Thanks for the feedback, this is something on our radar. One change we made recently is to make the Changelog more general rather than pinning it to a specific release version because we ship updates quite frequently. The idea is that rather than a user caring about whether the new feature is shipped in 3.14.1 vs. 3.15, we wanted to highlight the feature instead.
Regarding bug reports we always try to follow-up with the user who reported the bug when it is fixed / finished. Following or comment on these posts when you see them is a good way to be notified when the bug report is closed/fixed. I realize this is not a perfect system, but it’s not really possible to list all of the bug fixes in each release. Following up on the existing bug reports that we have and letting folks know when the fix is live is the best solution we have so far…
I understand and that makes sense. But I think you can do both similarly to how JetBrains does it. They have a “What’s new” blog post and a more detailed release notes page developers can look at.
It would be nice to see in a release what you are fixing even if they aren’t effecting me and I’m not subscribed.