What's the reason for the ongoing turbo release mode?

[speller]

Description

In a few weeks, the provider version has jumped from 4.x to 5.5. What's the reason for this turbo mode? Can it be more predictable? Versions are bumping significantly without fixing newly introduced bugs in previous recent releases. Could the authors clarify this, please?

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[justinretzolk]

Hey @speller 👋 Thank you for taking the time to raise this, and for checking in. We touch on this a bit in the FAQ section of our contribution guide. We generally try to stick to releasing one major version per year (as seen with the recent jump from 4.x to 5.x), and then generally release a new version once a week. Admittedly, we did release one extra version recently, to help with an announcement our recent HashiDays event, however, the pace of our releases has otherwise stayed fairly stable.

As far as fixing bugs, we have another document in our contribution guide that discusses how we prioritize. If we introduce something like, say, a regression, we try to label those issues as such, and tend to try to look at those things as quickly as we can. For more corner-case type bugs, we try to get to them as soon as we can, however, we fall back on the prioritization (based largely on reactions to bug reports) to try to determine the severity of a particular bug.

If you have any follow up questions, I'm happy to answer them as best as I can. Thank you, as always, for your feedback! I've seen you report a few issues lately, and while I know that takes time out of your day, those reports are extremely helpful to us, so we really do appreciate it.