-
Hello everyone!
The expected release date for Ubuntu Touch OTA-14 is Wednesday, November 4.
This forum post is a companion to the upcoming OTA-14 call for testing blog post.
Please post any general observations you have while testing the current image in the rc channel, as compared to OTA-13, in this thread. The current release candidate (rc) is 2020-W43
If you have any comments on any of the specific issues in the OTA-14 tracker, please post them in the issue thread so they are easier to track. OTA-14 tracker: https://github.com/orgs/ubports/projects/23
Please note that only critical and security fixes will be able to enter OTA-14 as this point, normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.
-
@UniSuperBox changed 13 to 14 on first line.
-
@UniSuperBox Hello, still new, still not sure how to contribute here.
I went through the list and was able to check some of the issues.
But for many entries I had no clue how to verify them. Maybe some are quite technical and I was even not aware of the existence of them at all.
I understand that some issues can be checked only by developers. But when ever you want to have a test by "users" a clear statement of the expected result would help, in my opinion.
And am I right, the basis for testing here is the RC channel?
I would like to say many thanks to all of the developer who are working to fight down the issues.
-
@Tellina said in OTA-14 Call for Testing:
And am I right, the basis for testing here is the RC channel?
Yes you're right.
RC is mainly used to release the code to users so they can test it and validate the work done.
So when it reaches the mass users (stable) there is no major issue or bad surprise. -
@Tellina when I don't know how to test them I always ask and they always answer me (after some time), than I follow the steps (see example).
EDIT: as @Tellina poited out (in private message):
Hi, thanks for your response. Well, don´t get me wrong, but I do not agree with "your" approach. Lets assume 100 persons are testing and following your way. The developer has to answer 100 (different) mails and might risk get answers which are not in line with the issue to test. This is why test cases should always consist of a description what to test and what the expected result is. Cheers
I forgot to mention. First I read the issue and all comments. If there is already a test description there, or I can figure out how to test, then I will not ask any question and just write my test results (with a decription what I tested).
Always read (everything), think twice and don't spam with unnecessary questions. That's one of my mottos.
-
On Nexus 5:
- Camera: switching from photo to video doesn't freeze the app anymore
- Morph browser: videos on LBRY are playing without interrupts now.
- uNav is too slow in acquiring the position, PureMaps finds it in seconds.
-
@C0n57an71n said in OTA-14 Call for Testing:
uNav is too slow in acquiring the position, PureMaps finds it in seconds.
The first fix can be slow, so if you tried uNav first then PureMaps it might explain what you noticed.
-
@Tellina said in OTA-14 Call for Testing:
But for many entries I had no clue how to verify them. Maybe some are quite technical and I was even not aware of the existence of them at all.
Just doing your normal activities and pulling up less used apps is testing, no news, is good news. Then report any issues arising after the change.
As a novice techie most all of these things are over my head, and my experience has been RC channel is remarkably stable. These devs are good at that.
-
I noticed that the regression of apps using QtWebEngine 5.14 not having autocorrect in their keyboards is still there.
-
Hi @Fla,
It is unfortunate that we didn't find that in time for OTA-13, but since it is already in stable I don't believe it is a reason to cancel this update.