From 6ba23e584089dc63e737461d45967786f39afb50 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 30 Sep 2026 17:10:34 +0000 Subject: [PATCH] Point the Google Play badge at this app's open testing The badge linked to de.qspool.clementineremote, the original author's app, which Play no longer lists. This app is org.clementine_player.remote, and until it's in production its only Play page is open testing's, where people join and install it. RELEASING.md says to switch the badge to the store page on going to production. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_012foWs5vBJrYTDtfyFhJ3ky --- README.md | 5 ++++- RELEASING.md | 4 +++- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bd79d039..284a55dc 100644 --- a/README.md +++ b/README.md @@ -43,9 +43,12 @@ Get Clementine Android-Remote: Get it on F-Droid - + Get it on Google Play +On Google Play, the app is in open testing for now: the link lets you join it, and install +the app. + This application is licensed under the GNU GPLv3. If you have questions, suggestions etc. please write an e-mail. diff --git a/RELEASING.md b/RELEASING.md index 9405f1f3..2a1cabe2 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -72,7 +72,9 @@ Play refused the upload, say), run it with that tag to publish it again. Closed testing*), and set up open testing (*Testing → Open testing*: the countries it's available in). The service account's *Release apps to testing tracks* permission covers both; releasing to production needs *Release to production* too, and `PLAY_RELEASE_TRACK` - set to include `production`. + set to include `production`. Then point README.md's Google Play badge at the store page, + `https://play.google.com/store/apps/details?id=org.clementine_player.remote`, instead of + open testing's. 4. If `v*` tags get a repository ruleset, let GitHub Actions bypass it: the workflow pushes the tags.