Migration path

[dbrgn]

Hi, as discussed in #67, this adds an info activity to users, indicating that they should switch to the new app:

Right now the new app is waiting for inclusion on F-Droid: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11526

For Google Play, I'll first have to create a new developer account and re-submit the app.

I think the best plan is to wait with merging until the app is released both in F-Droid and in Google Play. Then you merge and publish a last update to both distribution channels. @rorist do you agree with this plan?

[niccokunzmann]

If I would want the app to display that it is outdated, upgrading it to a later version means that only those who use a compatible Android to the latest version will be able to see the migration proposal - nice idea.

[dbrgn]

PR updated, just waiting for the Google Play identity verification process to finish, so that I can publish the app.

[dbrgn]

App is now published on Google Play! Screenshot of the final activity:

@rorist could you merge this, tag a version release and publish a final update to Google Play and F-Droid?

[dbrgn]

@rorist sorry to bother you! any idea, by when you could do the deprecation release? 🙂

[rorist]

Hello, thanks a lot for the work ! I'll check it asap, I have to dig up some backup for the release key as well ;)

[dbrgn]

@rorist Any news on this?

[dbrgn]

Hey @rorist! I hate to bother you again, but could you maybe take a look at this PR sometimes, as well as #90 (which updates the README)? We'd like to get users to move over, otherwise they'll be stuck with a version that doesn't receive updates and might stop working in the future.

That would be greatly appreciated (and I owe you a beer or mate when we see each other again) 🙂