I can confirm that I've been a beta tester since 2012 (how time flies!)
and, so far, have never had a problem attributable to running a beta copy.
I've had one corrupted file a long time ago (which I was able to fix by
looking through the xml file in notepad), but that won't have been due to
Hi Dan,
Thanks for your answer.
>What exactly would that mean for me? Are there some kind of expectations
>from me if I join (i.e. tasks / response times)?
Sure there are no tasks or response time :) You just install the builds
from the beta (not public) upgrade line and work with MLO as you
I have sent a reply to my last support email with the 2 backup files
(Desktop and Android). All tasks are deleted.
Thank you Dwight for the information.
Then yes please. I would be interested in joining the beta group.
Regarding Jira. You have your internal workflow which works for you. I
Dan, I recommend participating in the beta group. There's no minimum
participation requirement. Beta releases tend towards very good stability,
the downside is that sometimes the UI for new features can be clumsy when
they first appear. But I find it great to have the opportunity to influence
Hi Stéph and Andrey, thank you to you both for your answers!
Regarding the issue tracking. I thought that maybe a publicly available
issue tracker would be good.
This way it would be transparent to the customers what the status of
certain issues are.
Furthermore they could for instance vote so
Hi Dan,
Andrey is here, the developer. First of all, let me say that I am very
sorry to hear that you had issues with wifi sync.
You are right that such issues are very hard to deal with, especially if
you cannot reproduce the problem. From our experience in most cases, it is
related to the
Correction (pointed out to me by Dwight): *Jira *doesn't have the voting
thing - I was confusing that with *User Voice*, which MLO was using for
gathering users' suggestions and which has a flawed voting system for
checking popularity of the posted suggestions.
Jira is used by the MLO team
Dan, It sounds to me like you would be a perfect person to have on the beta
testing team! I wish I understood how to do the analysis you described
there.
Just one point - The MLO developers *do *run some issue tracking, on Jira.
I'm not convinced Jira has the best system for prioritisation of
I've figured it out and fixed it.
--
For anyone who is interested. The sync process initially syncs all the
delta data from Android to the PC. This worked flawlessly. Afterwards the
delta data from the PC to the Android device is synced.
Here always the problem occurred. It had
