ubuntu-phone team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

Hey,

So, we are nearly there, but first, let's talk about images. Image 50 
has been kicked out with the latest from the archive. This one contains 
notably some telephony fix to be able to receive SMS from special 
numbers. Tests results were especially good on image 49 (94.8% on mako 
and 96.5% on maguro), image 50 tests are still running, let's cross 
fingers! You are as well able to rename files through mtp :)

We are blocking any new submission like the toolkit update that was 
requested and had as well to kick back some merge proposals made to 
trunk on the components we need to land. This is only to focus on being 
able to promote the next image as soon as possible and it seems very 
doable now. :)

Indeed, on the promotion blockers:
> * qmlscene crash 
> (https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1243665) 
> + some apps not showing randomly (and reliably for the dialer app when 
> receiving a phone call): 
> https://bugs.launchpad.net/unity8/+bug/1257000. Upstart-app-launch fix 
> seems to not be trivial. We still hope for a fix before EOD.
-> We had a couple of hours ago the fix committed to trunk in 
upstart-app-launch. However, it is an API and ABI breakage and so, we 
are coordinating the landings of the reverse dependencies: unity-mir, 
content-hub as well as url-dispatcher. We just cherry-pick the fix for 
some projects where we are not confident with trunk state itself. All 
those builds/merges are happening as we speak + the qualification of the 
bug fixes before publication to the archive.

> * We'll have to make a full Unity8 release landing to get the fix for 
> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1257493 (another 
> blocker). This release is pending a late merge proposal to get it in a 
> releasable state. The landing team will land it as soon as it's ready.
-> The late merge proposal finally got it in the start of this 
afternoon, Unity8 is built and autopilot tests for all components are 
now run. So far so good, let's hope we can release it then.

As soon as those 2 batch of fixes are merged in, we plan to kick an 
image build and let the infrastructure do its test magic (so, an 
additional 6-8 hours). This image should then confirm that we are good 
for promotion again. Looking at the time of the day, the promotion will 
surely happen (if results are good) on Monday morning to not risk a bad 
week-end touch image.

We're near there, let's keep it up!
Cheers,
Didier