Replies: 5 comments
|
++ I was about to ask a similar question: could we get stable v2, and if there needs to be more breaking changes, release a v3? Instead of having multi-year-long alpha lines, accept breaking changes, write good release notes/migration guides and increment a number. (I know this doesn't help your case, but indirectly might help more adoption and maybe more contributions as well.) |
|
I'd love to know this as well, we currently depend on Paparazzi on our CI and it's blocking our ability to set our compile api level to 36. Alpha02 supposedly fixed some issues related to Android 16 and api level 36, but we're still seeing |
|
I'm also keen on this, I need to make changes to our snapshot integration and since the next milestone seems to have a bunch of big changes I don't want to spend a lot of work just to have to change it all again. |
|
For those tracking AGP 9 support: #2318 (Upgrade to Android Gradle Plugin 9.1.0) is open and targeting the 2.0.0-alpha05 release. |
|
When will the alpha 05 Release be released? It was originally planned for last Friday the 17.April. |
Uh oh!
There was an error while loading. Please reload this page.
Is there any timeline around the work being done for v2, and are alphas time or milestone based?
I'm in a bit of a tough spot with Paparazzi now, since I started using the v2 alphas because of #2026, but now v2 is broken because of #2111. When AGP 9 is released there will be even more issues.
All reactions