OTA-13 call for testing

Fla

pinging @lduboeuf on this one as he touched the SMS app in that release.

lduboeuf

@Fla
Filed an issue in messaging-app: https://github.com/ubports/messaging-app/issues/230
and a fix here: https://github.com/ubports/messaging-app/pull/231

But i'm afraid it won't land into OTA-13 sorry for that. As a workaround copy/paste should work

Fla

@lduboeuf said in OTA-13 call for testing:

But i'm afraid it won't land into OTA-13 sorry for that

I noticed a few weeks ago already, I should have reported it sooner, sorry.

However that looks like a blocker for me, I don't see all UT users with a regression like this one waiting for OTA-14... Especially if you already have a fix for it. But I guess that'd be @UBportsNews choice.

UBportsNews

@Fla Sorry not sure what you mean. We don't influence what is pushed through the OTA process. There is an update listed in the github link though https://github.com/ubports/messaging-app/issues/230 maybe @universalSuperbox knows more.

lduboeuf

@Fla
Yes, we are lucky, it is accepted for OTA-13

Fla

And the build is already pushed over the air, I now have the last RC and it fixes the problem. That's awesome, thank you @lduboeuf and @UniSuperBox !

UniSuperBox

Due to the need to release a new RC image and the tickets still waiting in the QA column, release has been pushed from Friday, September 4 to Wednesday, September 9.

lduboeuf

@UniSuperBox That is a wise decision, the call for testing was way too short before releasing

UniSuperBox

A critical issue was found in https://github.com/ubports/ubuntu-touch/issues/1556, "Text messages do not wake the phone."

Fixing this issue, releasing the fix into devel, and testing it for inclusion to rc is our highest priority. But given the high profile nature of the issue, we will likely not feel safe in releasing an RC before Wednesday, and we will definitely not feel safe releasing to Stable until after the RC is released and tested.

For that reason, Ubuntu Touch OTA-13 is again delayed, this time at least to September 16. We may need to further delay if the issue is not fixed in time.

Keneda

@UniSuperBox
Take the time you need to fix this without braking anything else, we have time...

Moem

@UniSuperBox We prefer a good release to a fast one!

Podgoro

Hammer head nexus 5

Native camera app doesnt work
front camera black screen
rear camera frozen screen

AppLee

@Podgoro

2020-w37 camera app is working fine.

Front and back camera OK
Video and photo OK

Only problem is an old one when switching between video and photo, the image is frozen. You have to swipe from the right, wait a couple of seconds then select the camera app back.

Podgoro

@AppLee in fact I'm back ota 12

AppLee

@Podgoro
It should also work in OTA12, but that's off topic here

UniSuperBox

Due to a critical issue found in the current RC, we have again delayed the release of OTA-13 to Monday, September 21.

This is precisely why we don't do 5-month update cycles...

lduboeuf

@UniSuperBox which critical bugs ?

Don't see anything here: https://github.com/orgs/ubports/projects/17

Fla

@UniSuperBox I didn't have new RC update since September 9th (2020-W37), am I missing something? If the release of stable is planed for this Monday, I expected another release candidate before that date...

Lakotaubp

@Fla There have been issues since the 2nd Sept then 7th as last Weds 16th was the release for OTA I guess that would explain the lack of any update since the 9th. The release was only stopped the day before on the 15th.

UniSuperBox

Apologies for the lack of detail in my previous message, but the reason for the delay was an embargoed fix for https://ubuntu.com/security/notices/USN-4519-1.

I have now pushed RC image 2020-W38.

Due to the contents of the PulseAudio change, we believe we can release safely on Monday (September 21).

However, a change has been merged to ubuntu-push during our freeze period, causing a rebuild. Since the last time ubuntu-push was rebuilt was a year ago, we are cautious around this component. It is possible that a change in one of its dependencies has caused a regression in its behavior on-device. During this period, please be extra-conscious of push notification receipt from apps like TELEports and FluffyChat.

I've run a variety of tests on devices using the pushclient example app in the store, so I'm fairly certain everything is fine. But please, watch this piece in particular.