-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Create new legacy version for API 16-20 users #333
Comments
I propose to use the release state 2020.08.21 as legacy base. |
@bekuno
It compiles and runs for me in emulator API 16. |
I created PR #343 with two change suggestions. |
Let me reopen this to track until release of a legacy version. |
AFAIR from c:geo the sequence for publishing a legacy (see also: cgeo/cgeo#8602 (comment)) would then be:
Logic should be: versionCode_oldrelease < versionCode_newlegacy < versionCode_normalrelease |
On the weekend my plan would be to do the following:
This should make the legacy version available to API 16-20 and the current beta available to API21+ |
Legacy version 2022.01.14-legacy (Code: 20220105) is part of the ongoing release. See #251 |
Current
release
is only working for API>=21 according to smoke tests.Therefore the minSDK has been raised to 21.
If we want to publish a version for API 16-20 users we need to update the
legacy
branch accordingly.I am setting the foundation for this next days by:
legacy
state intolegacy_API15
legacy
to the most current working state (seemingly before new settings have been introcuded)legacy
(i.e. New icon, User Agent fix, Hint for text input)When this is done we can try to work on a legacy release as described in #266 (comment)
The text was updated successfully, but these errors were encountered: