^^ that regression was introduced in 1.5.30-RC, re...

# eap

[Zac Sweers]

^^ that regression was introduced in 1.5.30-RC, reported on time, and then slipped and resulted in kotlin 1.5.30 being DOA for anyone using code that hits that issue (at least anyone using Wire). This is the second kotlin 1.5.x release to be DOA for us (1.5.0 shipped with a major memory leak in KGP), which puts it at 50% DOA on release since moving to this new release cadence. I'm quite concerned seeing regressions reported correctly in the EAP process not factored into this and reducing the reliability of actual releases.

I don't really have a question here, this is just feedback and I hope JB folks here are paying attention to this problem. It's quite demotivating to go through all the appropriate hoops to report issues only to see the release go ahead with them anyway. 😕

[serebit]

Not that I have any idea how internal development processes work at JetBrains, but perhaps more resources should be devoted to reviewing and squashing bugs found in milestones and release candidates, even if that means pulling resources away from developing a new minor release.

[elizarov]

Thanks a lot for finding and reporting the problem. It is our fault that we’ve underestimated the severity of this regresstion, so it was not considered to be a show-stopper for the release.