@kaimi@status.kaimi.cc Though technically possible, creating another "AndStatus Beta" application with its own Source code repository specifically for F-Droid would be an overkill...
As I see how F-Droid itself deals with their own client application: they simply use naming convention leaving to a User to decide if he or she wants to install something called "-beta1". Is this a proper approach to accept for AndStatus releases on F-Droid?! Taking into account that published by a Developer release appears in F-Droid apk repository several days later, I don't really think this could be convenient for Beta testing?! What's more, you never know, which "beta" will become a Production release, so it looks like F-Droid users should treat ALL releases as Betas and we don't need to change anything here?! Maybe this is why f-droid client application releases are always called "beta" or "alfa" - flawed process!
?!

Google uses approach that is far more convenient for developers and for users. You don't rely on names here at all, but three logical distribution channels exist: Alfa, Beta and Production. The same package after successful testing may be promoted by a Developer to the next channel, the package doesn't have to be renamed or resubmitted.
The same for a User: he subscribes to a Beta channel by setting a checkbox at a Google Play Web site and starts to receive both Beta and Production releases the usual way. I will send you a link to the # Open Beta testing channel as soon as I prepare new release for testing.

@deavmi@quitter.se @gallux89@quitter.se @gianf@quitter.se