OTA-12 Update
-
OTA-12 Update:
Due to a critical issue, we are extending the OTA-12 call for testing, and pushing back the official release date to the 13th May. This is to ensure that we deliver the best experience for our stable releases.
Thank you to all who have been testing. Please continue to do so while we prepare for this next release.
https://ubports.com/blog/ubports-blog-1/post/call-for-testing-ubuntu-touch-ota-12-273#OTA12 #UBports #UbuntuTouch #Ubuntu
-
Is this "critical issue" on RC too? What is it?
2015-Now : Meizu MX4 (ubp OTA-17) for daily use
Spare : Nexus 5 (ubp OTA-17) -
@Keneda hello, it is this issue: https://github.com/ubports/ubuntu-touch/issues/1437
-
@Keneda OTA-12 is the current RC channel. It becomes OTA12 when it moves to stable.
-
@Loops said in OTA-12 Update:
@Keneda hello, it is this issue: https://github.com/ubports/ubuntu-touch/issues/1437
Thanks.
I'm on RC with MX4 and didn't encountered this issue.@Lakotaubp said in OTA-12 Update:
@Keneda OTA-12 is the current RC channel. It becomes OTA12 when it moves to stable.
I know.
I assumed that before going RC, bug fixes and other improvments were tested on devel.2015-Now : Meizu MX4 (ubp OTA-17) for daily use
Spare : Nexus 5 (ubp OTA-17) -
@Keneda Things start in the Edge channel (really really start of process) then to dev( updates daily) that then moves on a weekly basis to RC. Thats where things get their final check and testing before becoming the fully stable OTA.
At any stage something may crop up to cause an issue , this becomes less likely the further down the line you get, which is why the call out for testing. I have not looked into this much but sometimes things only affect one or two devices but obviously they need ironing out. That is probably what happend in this case. -
That's why i asked if issue was on RC, because it was not sure, as work is in progress and RC gets OTA every week from devel validated work, so not obvious RC would be impacted.
2015-Now : Meizu MX4 (ubp OTA-17) for daily use
Spare : Nexus 5 (ubp OTA-17) -
Merging is not an easy task. When you merge part of code you may break things.
So see the channels as maturity levels.First you work on edge to add new features and make big chunks of changes.
Then at some point edge's code is merged to devel.There are more users using devel and they can contribute with less adventurous feature implementation or bug fixing.
When major features are working and seem stable enough a merge is done to RC.There more users can test without too much pain so more smaller issues are identified and fixed.
When a new bug is discovered you have to choose fix it in this release or it can wait the next OTA...Basically you can consider Edge, Devel and RC as the same code at the moment.
-
@UBportsNews
Thank for delay.
I have a problem with incoming calls (see OTA-12 call for testing forum) “starting“ from (rc) w18 (w17 was working OK, at least as OTA-11) and still present on w19 (yesterday released).Someone, in a way, could “sponsor“ the rc test on bq e5 (to those who own it)?
