Bacon goes focal!
-
First installer failure on another device. The device always booted to the recovery. Installed 16.04 stable fine.
-
Feels like this should be obvious, so apologies if I missed it. But I will try to take comfort that if I am unaware of something "everybody knows", then it's possible I am not the only one.
It is not a good use of time to test and report 'feature X still does not work' with each update, if no work has been done on feature X.
Where do we look up which features we should be testing with each release? (And could this information, or a link to it, be added to the opening post of each future 'open for testing' thread?)
-
@prophanetes I think a standard list of things to test (probably for each device) would be quite useful. It would need to be scaled for a) Developers b).........c)........d) standard users. Then a database could be put together to collate and process all this information...that seems kind of sensible (or some version of same) for workflow and areas that require attention etc.
-
@prophanetes You could just check all the working and non-working features on the device page for OpO on focal, and then report your findings here, ideally all in one post. We're also working on an issue tracker so that should make reporting bugs easier as well.
-
@TheVancedGamer But. If I am on R98, and then update to R99, which only includes changes to say, the camera, how do I know to focus my attention on testing the camera and not waste time trying to test the SIM, and spamming the thread about how the SIM doesn't work? I don't see any sense in continually testing features that won't have had any changes, and I am sure the community doesn't need to keep hearing about them.
-
@prophanetes You would know what to test, because I post in this thread every time I try to fix something and need input on it.
-
@TheVancedGamer Aha. Cool, thanks. Makes sense, but wasn't obvious.
So, what changed today when I updated from R62 to R78? What goes into a release is surely documented somewhere? Where do I find that?
-
@prophanetes It is not always that commits from @TheVancedGamer targetting this device gets included in updates, so there might not be anything worth testing in that update interval.
-
@arubislander Understood, but still doesn't tell me where to find what are the differences between releases.
-
@TheVancedGamer said in Bacon goes focal!:
@prophanetes You would know what to test, because I post in this thread every time I try to fix something and need input on it.
-
@arubislander Dude. If I am offered a 130MB update, more is changing on my device than just a version number. I am quite clear that not all of it is the work of the porter for my particular device. If you do not know where the information exists about what is changing between releases, please don't feel the need to quote responses that don't answer the question.
-
@prophanetes O, you are no longer refering to the differences for this device, but the differences in general. There is no one accessible source of truth for this. But there is this which goes some way in giving an idea
-
@arubislander That is a lot closer, but unfortunately I have ended up lost in a maze of repositories at GitLab several times, and given up. I imagine there would be page somewhere, even if it was manually maintained, linking a Release number with all the Merge Requests that went into it.
@Dunbrokin said in Bacon goes focal!:
@prophanetes I think a standard list of things to test (probably for each device) would be quite useful.
I wish I had've found this sooner myself, but https://docs.ubports.com/en/latest/contribute/quality-assurance.html contains a link to a spreadsheet which explains how to test each feature. (I can't tell when it was last updated/reviewed. The way everything is laid out into a grid for recording test results almost looks like it was meant to be submitted somewhere once complete... but the instructions are to head to the issue tracker on GitHub.)
-
@prophanetes said in Bacon goes focal!:
I imagine there would be page somewhere, even if it was manually maintained, linking a Release number with all the Merge Requests that went into it.
Manual maintenance would be impractical to the extreme. With the frequency of builds and updates to the development channel (which is the one that works with release numbers) it would require updating daily to keep pace. I can't imagine anyone volunteering to do that for any amount of time to make a difference.
There was a proof of concept made, by @TheVancedGamer if I recall correctly, to generate an automatic list of MR's that went into a build. But I am not sure what became of the initiative.
-
r90 update hoses the system with a screen size issue. The text is too small to read. It was a swine to install too. I am currently trying the installer to see if that solves it. The display crashes a few times before reverting to tiny text.
-
since three days the scaling is wrong, so the device is not operable. I've tried the installer last two days but it is allways the same
-
@thoralf68 Unfortunately this is a regression in the main rootfs, so this bug is affecting all devices currently. Best that we can do is wait and let the core devs fix the issue
-
Some are posting the same issues on other devices, thanks for the heads up @TheVancedGamer
-
Just a quick heads-up: the 20.04/devel channel seems to have broken without us noticing. We're (more like me :P) trying to investigate it. In the meantime please avoid updating until the issue is resolved. Thanks!
-
@TheVancedGamer Thanks for letting us know. Have been waiting for a fix.
