ubuntu-phone team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

Hey,

What a way to end the week… All tests failing, heroic fixes at 5AM from 
Alexander and Ricardo and now an ubuntu Touch image which is a promotion 
candidate! Excited? Let's start!

#224:
* terminal-app has the test fix as well due to new font size
* click itself had a new release
* contains the click package conversions discussed yesterday (camera and 
gallery). Unfortunately, all tests were failing on gallery due to a 
wrong path. This is now fixed in #226.
* the telephony service and system settings are now both reading ring 
tones and various settings from the generic accountservice rather than 
gsettings
* a lot of platform changes (android-tools, gtk, codecs, python3.3, 
syncevolution, networkmanager…)

This image had an issue on the test side: no test started because 
unlocking the greeter didn't work during the tests (due to a missing 
dependency). As the procedure for rerunning the whole testsuite wasn't 
known, a new image (after the CI change has been reverted) was kicked 
in. This has triggered some discussion on how and who should unlock the 
greeter properly.

#225:
only one change: qt5-organizer-eds with a partial fix for the alarm 
clock on Sunday (bug #1285958), which starts to be a serious contestant 
with the other well-known bug "libreoffice can't print on Tuesday" from 
some years ago :)

-> the tests results on that one was similar than previously, apart from 
the gallery-app testsuite failing due to the click package version

#226:
* the gallery-app test fix to rock and roll fully now as click packages! 
(so the issue mentioned above should be fixed)
* some weather-app fixes as well. Should still see minor bugginess, but 
they are acceptable.
* You can now use: "setprop persist.service.ssh true" to have ssh 
starting by default on the image!

-> tests and really serious dogfooding are happening as we speak.
After more investigation, the notes-app test issues have very low impact 
on the user experience compared to latest promoted image. We decide to 
not block on the tests failing on that anymore, knowing that there is no 
end-user final change (alarms were already not working on latest 
promoted image). The sdk team is still working on getting it fixed though.

So to sum up, we should expect on #226:
- the Qt 5.0 related to V8 crash
- weather app bugginess
- alarm/clock app remaining issue which are not fixed by #225 (not a 
regression from latest promoted image)

The QA team, in addition to the dogfooding, is analyzing the exact user 
impact and frequence of crashes to assess if this image will be 
promotable or not. The floor is opened to them.
We'll probably take the finale image promotion decision based on their 
input on the crash, the dogfooding outcome, and the image AP test 
results on Monday then.

Happy week-end everyone!
Cheers,
Didier