Beta testing of AndStatus #456

Open
yvolk opened this Issue May 5, 2017 · 8 comments

Comments

Projects
None yet
2 participants
@yvolk
Member

yvolk commented May 5, 2017

Please note that the most convenient way for Beta testing is to opt in as a Tester at Google Play: https://play.google.com/apps/testing/org.andstatus.app
Unfortunately F-Droid doesn't have a notion of Beta release/testing yet...

If you don't use Google Play, for Beta testing I'm attaching the latest Beta release of AndStatus to this post.
The apk file inside the zip is signed with the same keys as in Google Play. I.e. in order to test the application you may be prompted to uninstall existing AndStatus application, downloaded from other sources (e.g. from F-Droid).

AndStatus has Backup/Restore feature, so you can Backup your current configuration and messages before uninstall and restore them after installation of the new version. Please note that attachments and avatars will not be backed up and restored, but AndStatus will re-download them on demand (e.g. if you scroll to an old post) of course.

Before installation of the below linked AndStatus package you have to unzip it first. This is .apk file that should be installed. I use "Total Commander" for unzipping.

2018-06-18 v.40.02 Release. Android 7.0+ only. "Note Editor UI improvements"
AndStatus-40.02-release.zip

See the Change log: http://andstatus.org/changelog.html

2017-08-13 v.35.06 Release. Android 4.4+. AndStatus-35.06-release.zip

Unzipping Android package using Total Commander application
screenshot_2018-04-23-08-30-51-682

@yvolk yvolk changed the title from Beta testing for people, who don't use Google Play to Beta testing of AndStatus for Google Play users and for people, who don't use Google Play May 5, 2017

@licaon-kter

This comment has been minimized.

Show comment
Hide comment
@licaon-kter

licaon-kter May 30, 2017

Unfortunately F-Droid doesn't have a notion of Beta release/testing yet...

Did you see the "Enable unstable builds" toggle in Settings? That's what you want. ;)

Basically you make a new tag here 33.09-beta, and add it to the metadata there BUT you don't update the last version. eg:

Build:33.09-beta,217
        commit=33.09-beta
        subdir=app
        gradle=yes
...
Current Version:33.08
Current Version Code:216

There isn't any specific info about this, except a bit here (and inspiration from other apps metadata).

Unfortunately F-Droid doesn't have a notion of Beta release/testing yet...

Did you see the "Enable unstable builds" toggle in Settings? That's what you want. ;)

Basically you make a new tag here 33.09-beta, and add it to the metadata there BUT you don't update the last version. eg:

Build:33.09-beta,217
        commit=33.09-beta
        subdir=app
        gradle=yes
...
Current Version:33.08
Current Version Code:216

There isn't any specific info about this, except a bit here (and inspiration from other apps metadata).

@yvolk

This comment has been minimized.

Show comment
Hide comment
@yvolk

yvolk May 30, 2017

Member

@licaon-kter I didn't hear that a developer can change his application's metadata in f-droid repository.
How do I do that?

Member

yvolk commented May 30, 2017

@licaon-kter I didn't hear that a developer can change his application's metadata in f-droid repository.
How do I do that?

@licaon-kter

This comment has been minimized.

Show comment
Hide comment
@licaon-kter

licaon-kter May 30, 2017

Anyone can, so many apps, not that many devs... Eg. my merge request

Your app is on "auto-update" so if you publish a release tag, it will be picked out. But if you want to add some text (like I did) or add an unstable version you need to intervene.

Workflow:

  • Go to the repo: https://gitlab.com/fdroid/fdroiddata
  • Login to Gitlab via Github
  • Fork it
    (The text below covers the process to edit something using the web interface, you can now use git of course to edit/push commits)
  • Go to Repository - Files - search "andstatus"
  • View file
  • Press Edit
  • Make changes
  • Press Create branch - name it
  • Uncheck "make merge request" for now
  • Press commit
  • In the commit see Pipelines (for the CI run that was triggered)
  • Press on the running one -> lint -> wait for it to finish (usually lint will error out on some space or something, you'll need to make a new commit that hopefully fixes that...rince, repeat; this is why I've said to uncheck the make merge checkbox because it would create one even if lint fails :()
  • When lint is ok, when looking at the branch-> merge requests->create (fdroid/reponame - you/reponame )- done
  • Wait for it to be merged by the devs

Anyone can, so many apps, not that many devs... Eg. my merge request

Your app is on "auto-update" so if you publish a release tag, it will be picked out. But if you want to add some text (like I did) or add an unstable version you need to intervene.

Workflow:

  • Go to the repo: https://gitlab.com/fdroid/fdroiddata
  • Login to Gitlab via Github
  • Fork it
    (The text below covers the process to edit something using the web interface, you can now use git of course to edit/push commits)
  • Go to Repository - Files - search "andstatus"
  • View file
  • Press Edit
  • Make changes
  • Press Create branch - name it
  • Uncheck "make merge request" for now
  • Press commit
  • In the commit see Pipelines (for the CI run that was triggered)
  • Press on the running one -> lint -> wait for it to finish (usually lint will error out on some space or something, you'll need to make a new commit that hopefully fixes that...rince, repeat; this is why I've said to uncheck the make merge checkbox because it would create one even if lint fails :()
  • When lint is ok, when looking at the branch-> merge requests->create (fdroid/reponame - you/reponame )- done
  • Wait for it to be merged by the devs
@yvolk

This comment has been minimized.

Show comment
Hide comment
@yvolk

yvolk May 31, 2017

Member

Thank you for information. I will definitely use this way to update Description of AndStatus application in F-droid. But manipulation with beta versions is inconvenient.
One of incompatibilities with my current release process is the following: when I create potential "release", I initially make it available as a Beta. If the Beta is OK, I "promote" it to a Release ("production") without any changes and without any new commits in the source code repository. F-droid cannot work this way now: as documentation states: "At the very least, the version name, version code and commit will be different"

Member

yvolk commented May 31, 2017

Thank you for information. I will definitely use this way to update Description of AndStatus application in F-droid. But manipulation with beta versions is inconvenient.
One of incompatibilities with my current release process is the following: when I create potential "release", I initially make it available as a Beta. If the Beta is OK, I "promote" it to a Release ("production") without any changes and without any new commits in the source code repository. F-droid cannot work this way now: as documentation states: "At the very least, the version name, version code and commit will be different"

@licaon-kter

This comment has been minimized.

Show comment
Hide comment
@licaon-kter

licaon-kter Jun 1, 2017

You would need to publish a new (non-beta) tag on Github, yes.

You would need to publish a new (non-beta) tag on Github, yes.

@yvolk

This comment has been minimized.

Show comment
Hide comment
@yvolk

yvolk Jun 1, 2017

Member

@licaon-kter As I understand above cited documentation, new tag for the same version number will not work. So I will have to increment version code, change version name and create a new commit?!

Member

yvolk commented Jun 1, 2017

@licaon-kter As I understand above cited documentation, new tag for the same version number will not work. So I will have to increment version code, change version name and create a new commit?!

@licaon-kter

This comment has been minimized.

Show comment
Hide comment
@licaon-kter

licaon-kter Jun 1, 2017

No really a commit, afaik, a new tag would do it.
Again, this is what I've inferred from other metadata.

Try to add your voice here too: https://gitlab.com/fdroid/fdroid-website/issues/71
Ping @pserwylo @krt16s

No really a commit, afaik, a new tag would do it.
Again, this is what I've inferred from other metadata.

Try to add your voice here too: https://gitlab.com/fdroid/fdroid-website/issues/71
Ping @pserwylo @krt16s

@yvolk

This comment has been minimized.

Show comment
Hide comment
@yvolk

yvolk Aug 13, 2017

Member

@licaon-kter In order to foster F-Droid support of Beta releases, I posted my vision of the target process to the relevant F-Droid's change ticket, see: https://gitlab.com/fdroid/fdroidserver/issues/161#note_37431690

Member

yvolk commented Aug 13, 2017

@licaon-kter In order to foster F-Droid support of Beta releases, I posted my vision of the target process to the relevant F-Droid's change ticket, see: https://gitlab.com/fdroid/fdroidserver/issues/161#note_37431690

@yvolk yvolk changed the title from Beta testing of AndStatus for Google Play users and for people, who don't use Google Play to Beta testing of AndStatus Oct 6, 2017

This was referenced Dec 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment