Thanks to all the hard work from our contributors, Lubuntu 20.10 has been released! With the codename Groovy Gorilla, Lubuntu 20.10 is the 19th release of Lubuntu, the fifth release of Lubuntu with LXQt as the default desktop environment.
We are pleased to announce that the beta images for Lubuntu 20.10 have been released!
While we have reached the bugfix-only stage of our development cycle, these images are not meant to be used in a production system. We highly recommend joining our development group or our forum to let us know about any issues.
Getting the download
You can download the Groovy Gorilla daily build here.
Recording the results
To record your testing, you’ll need a Launchpad/Ubuntu One login. Go here to create one if you haven’t already got one.
Our current behavior when we run a QA-test install is to use the “Install using Calamares (entire disk)” testcase, where in the Comments section we use the first line to briefly list hardware used, the second line has an entry like
Lenovo V14 IIL,Intel Core i3-1005G1,8GB,256GB SSD Testcase:BIOS,no encryption,full disk,Internet
which highlights it was a BIOS install, no encyption, full disk with internet connected; all of which matches an testcase found on our checklist.
How you describe your hardware is up to you, I get details from
sudo lshw roughly in format “Make model (cpu, ram, gpu)” so my x201 will show as
lenovo thinkpad x201 (i5-m520, 4gb, i915)
but in my testcase example I’ve copied the first two lines from a real QA-test install performed by our most recent Lubuntu member Leó Kolbeinsson.
Follow the directions in the testsuite. If it does all of those things, great! If it doesn’t, we do need your help. Please file a bug on your testing box, and record the bug ID in the Bug (or Critical Bug) section in the iso.qa.ubuntu.com page when complete.
Follow the directions in the bug report, and be as specific as you can. This is a key step – an unreported bug will be an unfixed bug. For details on reporting bugs please refer to our wiki page and don’t forget to include the bug report number in the iso.qa.ubuntu.com test report.
Please note tests that complete okay with only minor issues should still be PASSED, but the bug ID reported in the “Bugs” section. If you consider it a show-stopper bug, record it in the “Critical bugs” section (failing the test if you believe absolutely necessary).
Thanks in advance to those of you who can help, and please reply on discourse with any issues, concerns, or questions!