-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.11 Release (tracking) #5430
Comments
Sounds good |
Just a note that with the PR backlog representing a sufficient amount of instability, 2.10 will be a "fast-follows" on 2.9 focused almost exclusively on getting refactor PRs merged and stabilized (almost done here) and releasing in order to zero the translation straddle again before we strand any users with minimum SDK changes So I'm changing this to 2.11 as that will be where I open a merge window for new features |
Personal goals for 2.11 (assuming the number of bugs drops due to 2.9.6 and we're virtually crashless):
|
as volunteers we mostly continue working on what we want, so it's useful to express personal priorities (and encouraged!) but mostly this is happening on Discord right now on the anki server in the ankdroid dev channel. Feel free to hang out there or if that isn't comfortable you can always comment here or open an issue and propose something you want to work on |
With 2.9 in beta and nearly released #4961 - I wanted to start thinking of 2.10 [edit: 2.10 will focus on internal refactors + stabilization - 2.11 will have new features]
There is already a 2.11 milestone with things bumped from 2.9: https://github.com/ankidroid/Anki-Android/milestone/12
As for new ideas, I can think of these things:
More than anything I'd like to mop up 2.9 items (once 2.9 is stable and released), keep it focused, and get a faster public release cadence going.
Philosophically, maybe it's just one feature per release even, keeping it very small so features go out more quickly, and whatever pain points are involved in a faster release cycle are examined and targeted for improvement so it's really easy? That's my preference anyway, small frequent change.
Open to any thoughts of course
Here's our installs by API for the older APIs:
For reference, in our Compat infrastructure, there are 25 APIs total, and moving from minSdkVersion 15 to 19 would allow 10 to be removed at a cost of 10,000 users total. API20 was for Android Watches only, API21 / Android 5.0 as a minimum would allow a further 6 Compat APIs to be removed, At the cost of 25,000 users.
The text was updated successfully, but these errors were encountered: