-
Notifications
You must be signed in to change notification settings - Fork 1
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
RC notification should have target URL to Google Play #8
Comments
This is not as simple as changing a string, as |
Also not everyone uses Google Play. |
I suggest to trigger the notification manually (like for release) and target to Google Play. If we continue using the Google Play beta channel (what would be my goal) we will probably no longer actively promote the direct download. @SammysHP |
We had some questions of users who have installed the beta via Google Play and have clicked on our notification and got alerted by their device about unsafe installation (unknown source) which they considered suspicious. I think as Beta on Play will be used in future we should change the target and push it manually as suggested before. Any objections? |
Right now, when we build a release from the CI, it registers a "deployment" status until we make a "release" notification (so that we can follow early deployment stats before notifying people to update and still see people using the previous release). Similarly, we should change the CI so that it registers a "rc-deployment" status until we make a "rc" notification, right? And as a new release removes the deployment entry, a new RC should remove the rc-deployment entry. |
Sounds good |
What has been done:
|
Now that we use Google Play beta channel for RC versions it could be better to target the "New RC available" notification to the standard c:geo Google Play URL (like for new release) instead of our own download server.
Advantage:
The text was updated successfully, but these errors were encountered: