ruffle-rs / ruffle-rs/ruffle-android
suggestions for non alpha/beta version actions workflow
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 569
- Forks
- 60
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 16
Description
https://github.com/torokati44/ruffle-android/actions/runs/3680924426
wait for 3 months,it will be expired
we have to register an account to get download link
you're busy or dead, we won't get latest version
i have two suggestions
1.0 version:
release page
https://github.com/torokati44/ruffle-android/releases
- upload a release build when you have no spare 3 months
- update and generate a latest release build (keep only one release version) automatically, previous version will be replaced.
But I'm not sure, I download some Android apk from other repository. I have to uninstall current version to install latest version because they're different signatures. I hope this won't be happened if you know how to avoid that.
1.0.1+ version:
merge into official ruffle repository, apk files will be created daily. And they can be updated without uninstalling
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked GitHub Actions run and the repository's Releases page. The issue proposes several release and signing strategies but names no workflow file, test, or chosen outcome; done would require an agreed approach for distributing current APKs and handling updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- ci-cd, mobile-dev, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100