A modern programming language that makes developers happier.

kotlinlang

I was curious to learn more about what the is like for how Google Issues are handled related to Compose Android, particularly regarding the prioritization and release of issue fixes. There has been a <https://issuetracker.google.com/issues/254115946|longstanding issue> requesting the ability to set the dispatcher that controls composition during a UI Test to the StandardTestDispatcher. Recently, a <https://android-review.googlesource.com/c/platform/frameworks/support/+/3208355|pull request> was submitted to address this issue, and I was interested to see if it improved the stability of some of the end-to-end tests my team at work has developed – which it did. I am aware that there is a release cycle and that the PR requires approval. Could anyone provide insight into the typical timeline post-approval of a PR? Additionally, is there a specific target for completing certain features within each release?

Typically, once a PR is merged, it goes into the next alpha / beta release of that Compose library.

So new bug fixes/PRs are still able to come in once the current version has been bumped to a beta release even if it's unrelated to anything in the alpha releases?