Open Beta

[Marcus Wolschon]

Google has introduced more options for the Beta program in play store.

We currently don't have a beta there and all members of this Google Group mailing lsit may join.

Do we want to change this to an Open Beta, where everyone who has the link may join without having this mailing list as a shared comunication medium that reaches all beta testers?

What does everyone think?

Marcus

[Stephan75]

Hello Marcus,

I would say YES to an OPEN beta ... because my observation is that the amount of bug reports for the beta releases so far, and for final releases is quite low.

So it would not be bad to get as much beta testers as possible with a low entry level.

We can go that way for some weeks and see what will happen: more benefit or bad experience. Then switch to more restrictive beta testing group if needed.

In comparison to for example Osmand, the number of new issues for vespucci in github tracker is quite low so far, or not?

Tell us about any beta release, then we can publish that as a news item on Wochennotiz or weeklyosm.eu

Greets, Stephan

PS: to all OSM editor enthusiasts: did you here about the new release of Merkaartor 0.18.2 for desktop PC?

After some years of silence we have new releases ... 

but it needs improvements in some areas, especially UI ... see http://merkaartor.be for more information and downloads.

[Simon Poole]

Sorry for the late answer was away for a week.

I'm a bit on the fence ... in principle I naturally have nothing against more people participating in a slightly more formal beta testing, on the other hand the feedback is really really really low as is, and it is not clear to me if anything will change that.

Simon

--

---
You received this message because you are subscribed to the Google Groups "osmeditor4android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmeditor4andr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stephan75]

Hello Marcus and Simon,

as taking part in the "new" beta testing option, I receive updates for verspucci maybe every week or 14 days, I would estimate.

But when looking at the version string and version date in GooglePlay (as soon as an update for that beta is available, I see:

version: 0.9.7.0.1062  with a date: 07.09.2015

Although I am sure that each beta version has a more recent timestamp than 07.09.2015, or not?

As I am not aware about the tagging and marking of an app when having it on github and on android developer console:

Is there a possibiliy to mark all BETA releases like "0.9.7.0.1062beta" or similar,

and to have the date timestamp when that specific beta apk file was published?

Or am I wrong in some assunptions about your workflow?

Stephan:

PS If you want to increase feedback about Vespucci beta versions or even main releases,

tell us more about specific changes in app, and we ad soem thing more to the popular OSM channels like weeklyOSM oe Wochennotitz

(a news item about the new vespucci.io website is already in the pipeline) 

[Simon Poole (Google)]

1062 is from this week and current. The current convention is that the textual app id is 0.9.7b1062 b for beta and the numeric id (amazon is picky about characters in it) is 0.9.7.0.1062 0 for beta.

The website has release notes which are updated for major changes.

Simon

--
Diese Nachricht wurde von meinem Mobiltelefon mit Kaiten Mail gesendet.

[Simon Poole (Google)]

BTW news is nearly always available from the twitter account.