### Testing Versions
* Current development is on Lubuntu 19.10 [Eoan Ermine](https://wiki.ubuntu.com/EoanErmine/ReleaseSchedule). Lubuntu 19.10 is scheduled to release in October 2019.
* Lubuntu point releases are maintenance releases, do not expect too many changes. Daily testing and milestone esting will be needed here. See the release schedule for [Bionic Beaver](https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule).
### Current Supported Releases
The current supported releases are below:
* **Current stable release:** [Lubuntu 19.04](https://lubuntu.me/disco-released/) (Disco Dingo), supported until January 2020 (LXQt)development is on Lubuntu 19.10 [Eoan Ermine](https://wiki.ubuntu.com/EoanErmine/ReleaseSchedule).** Lubuntu 19.10 is scheduled to release in 17 October 2019.
* **Current Long Term Support release:** [Lubuntu 18.04.2](https://lubuntu.me/bionic-2-released/) (Bionic Beaver)Maintenance development is on Lubuntu 18.04 [Bionic Beaver](https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule).** The next scheduled point release, Lubuntu 18.04.4, supported until April 2021 (LXDE)is scheduled to release 6 February 2020.
# General information
The QA/Testing Team# General information
## What we do
The QA/Testing Team (which is informed by the [main Ubuntu QA team](https://wiki.ubuntu.com/QATeam)) is responsible for using formal test cases to check images of Lubuntu. This allows the [Release Team](https://launchpad.net/~lubuntu-product-managers) to easily gauge the health of the images. This makes it possible to tell whether an image is functional enough to justify a release and determine where resources need to be allocated to make sure an image gets released.
Other tests may be organized around application testing, new features, bug fixes, etc., This makes it possible to tell whether an image is functional enough to justify a release and determine where resources need to be allocated to make sure an image gets releasedbut the primary and most significant role of the QA team concerns images.
TThis testing consists of:is split into two main types:
1. **Testing milestone images**: Our most important job is preparing for release. A few days before a milestone is due (according to our [release schedule](https://wiki.ubuntu.com/Releases)), the daily image is selected and becomes the QA (Quality Assurance) test version (these are called Alpha, Beta, and Final, depending on the stage of the release cycle). Once it is confirmed that the release candidate works, it then becomes the released version.
1. **Daily image testing**: Daily images are constantly being tested to give us an early warning notice of any problems that could affect Milestone releases. This also gives us an opportunity to do more heavy testing to discover any bugs we hadn't noticed before.
1. **Specific testing**: Specific testing allows us to help with development.
All release stages are tracked by [the ISO Tracker](http://iso.qa.ubuntu.com/) where you can get the latest builds, see and allocate any bugs, and formally report testing results.
For more information about testing, please see the [main Ubuntu QA team](https://wiki.ubuntu.com/QATeam).
The most important thing to do is to always be on the lookout for [bugs](https://phab.lubuntu.me/w/bugs/)!
# Daily Builds
These ISOs are automatically generated every 24 hours using the latest updates on the system. They are available from [ISO tracker](http://iso.qa.ubuntu.com/). They are there to check that bugs that are resolved between the Milestone releases do not break the install. They also are used to confirm that any fix for a bug that seriously affects an initial install which is released for testing now works. Daily builds are suspended hen pre-milestone testing is being carried out. There is a [process](https://wiki.ubuntu.com/NewReleaseCycleProcess) for re-initiating the dailies after the cycle is over. Assuming we have a name, it should happen fairly quickly, as it's dependent on that.
Make sure to check for previously reported bugs and include them in your results if they're still applicable!
# Milestone releases
Alpha,**Testing Milestone images**: Our most important job is preparing for release. Beta and Final (formerly known as Release Candidates (RC)) are also tested using [ISO trackerA few days (usually two) before a milestone is due (according to our [release schedule](http://iso.qas://wiki.ubuntu.com/).Releases)), If you want to help out in this important area of testing,the archive is frozen and Daily images stop being produced. please read [Procedures](https://wiki.ubuntu.com/Testing/ISO/Procedures)The most recent image becomes the test image for further detailsthe Milestone. These appear a couple of days before the actual Milestone release so that we can check they are okay to become Milestone releases.
When a Milestone release passes the QA testingre called Beta, it becomes a Milestone Release and is listed on the [Releases](http://cdimage.ubuntu.com/lubuntu/releases/) as such.
Note this also includes point releases on LTS versions.and Final, Basically,depending on the stage of the release cycle. a point release brings in all the various bug fixes into one 'new' image. o get in to the build they have to pass [SRU](https://wiki.ubuntu.com/StableReleaseUpdates) testing.
If you would to know more about how this all worksWhen all images pass testing, have a read of [Stages of testing](https://wiki.ubuntu.com/QATeam/Overview/TheStages).
Make sure to check for previously reported bugs and include them in your results if they're still applicable!
the Final Release image is published.
## Getting Involved
* Get a Launchpad account and j1. **Join the [Lubuntu QA](https://launchpad.net/~lubuntu-qa) team** (you'll need a Launchpad account).
* 1. **[Join the main mailing lists](http://lubuntu.me/links/)**, specifically lubuntu-devel. Announcements often end up here, especially lubuntu-develso it's pretty crucial.
* Join #lubuntu-devel on freenode (IRC), [@lubuntudevel on Telegram](https://t.me/lubuntudevel),1. or [#lubuntu:disroot.org on Matrix](https://chat.disroot.org/#/room/#lubuntu:disroot.org) (which is all bridged to the same place).**Read the following tips for success.**
* 1. **[Start your first test](https://wiki.ubuntu.com/Testing/ISO/Walkthrough)!
### Before you get started
This section is dedicated to the current development version of Lubuntu.**
1. **Do not hesitate to [reach out](http://lubuntu.me/links/) and ask questions.** The mailing lists, chat, As with all early milestones,and forums are all good methods. **they are not suitable for a production environment**.We're here to help!
Whenever you are testingIMPORTANT: All release stages are tracked by [the ISO Tracker](http://iso.qa.ubuntu.com/) where you can get the latest builds, see and allocate any bugs, and formally report testing results. //**It is essential to record all results on the ISO Tracker.**// Sending a report on the mailing list is great, but if you don't also record the results on the tracker, keep in mind these few notes:it is challenging to collate all the data.
WARNING: The most important thing to do is to //**always be on the lookout for [bugs](https://phab.lubuntu.me/w/bugs/) and report them whenever you find them!**// Also, make sure to check for previously reported bugs and include them in your results if they're still applicable!
## Tips for success
1. * **Using a development milestone is not suitable for daily production machines.** That is why, That is whyto play it safe, to play it safe, it's better to use [virtual mmachines](https://help.ubuntu.com/community/VirtualMachines), spare testing machines, and/or USB drives, especially with early milestone releases. Beta milestone releases are a bit more stable, but are still under heavy development to ensure the highest quality release possible.
1.* **Testing on bare metal is important, **The most important part of testing is to actually install the system and check how the installation process will work**. This is very important. Also,too.** Some bugs are hardware dependent and would not be revealed if we only used virtual machines. if you have an early milestone installed installedThis necessarily requires wiping the data from that machine, it is less so make sure to [backup your important data](https://helpful to just upgrade. Please,.ubuntu.com/community/BackupYourSystem). do a fresh install.
1* **The most important part of testing is to actually install the system and check how the installation process will work.** This is very important. **//Always//** make sure to [check the hashes](https://help.ubuntu.com/community/HowToMD5SUM) of the downloaded ISO as well as the media it's installed onUnless you're specifically doing a testcase on upgrades, don't upgrade. If either is off by a single bitFresh installs only, it can cause all sorts of inexplicable problemsplease.
1. Most of the testing is done with [virtual machines](https://help.ubuntu.com/community/VirtualMachines), but if you want to install to a hardware system, that's helpful, too. If you do this, make sure to **[backup your important data](https://help.ubuntu.com/community/BackupYourSystem)**. If you are using Linux, the best and easier way is to make a copy of your `/home` folder or partition. If you want to do a full system backup, please see [this link](https://help.ubuntu.com/community/BackupYourSystem).
1. To save downloading the whole iso again for the testing version, simply copy your trusty image of what ever architecture replacing the old codename with the new one, e.g. 'trusty' ith 'utopic' and use [zsync](https://help.ubuntu.com/community/ZsyncCdImage). zsync also does automatic checking of the integrity of the image.
### What to do when
Familiarize yourself with the [release schedule](https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseSchedule). The dates listed for the release of milestone images are typically on **Thursday**. Two days before that, on **Tuesday**, release canidate images are made available for final testing.
Be sure to watch out for point releases on Long Term Support images, too. They often come in the middle of cycles on the development release.
We must have formal testing done and any showstopper bugs resolved within the two days. This doesn't allow for a lot of room for errors. Because of that, it is imperative that the week before official testing opens up, we do daily testing. Make sure to report all successes, failures, and bugs on the ISO tracker.
Note that dailies are off during milestone testing and get turned on shortly after release. The Release Team's schedule for the [milestone process](https://wiki.ubuntu.com/MilestoneProcess) can provide more information. Please consult this before asking them to turn the dailies back on.
It takes a little longer for the dailies to get turned on after a final release due to steps that will allow for development in the new cycle. This can take up to two weeks, so please be patient. For more nformation, please look at the Release Team's schedule for the [new release cycle process](https://wiki.ubuntu.com/NewReleaseCycleProcess).
### When images build
When turned on, dailies build automatically according to [a cron job](http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/etc/crontab). Look for the line with `for-project lubuntu cron.daily; for-project lubuntu cron.daily-live --live` and the time will be to the left in the form `MM HH * * *`.
The Alternates take approximately 30 - 45 minutes to complete. The Desktops take approximately 90 minutes to complete.
You can also see the status of images at https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/RELEASENAME/lubuntu (change RELEASENAME to something like trusty, utopic, vivid, etc). Note if it says successfully built, that does not mean it's uploaded to the tracker yet.
You can also see the [logs of automated builds](http://people.canonical.com/~ubuntu-archive/cd-build-logs/lubuntu/). This is a good way to troubleshoot why an image is not there.
Jenkins runs automated tests. In particular, there's [one that deals with Ubiquity](https://jenkins.qa.ubuntu.com/view/Ubiquity/view/Lubuntu/) that would be a good way to see if we're having problems with the Desktop ISO.
# Problems with images
If you do notice that builds are not appearing as expected, please let us know in our IRC/Telegram/Matrix channel linked above.
* All of the architectures or types not being represented* **//Always// make sure to [check the integrity](https://help.ubuntu.com/community/HowToMD5SUM) of the downloaded ISO as well as the media it's installed on.** If either is off by a single bit, it can cause all sorts of inexplicable problems.
* Old daily versions (the version in the form YYYYMMDD should be today's date).
# Packaging issues
### Unwanted packages
Some packages can be automatically installed, but are not wanted on a default installation. To find the package which automatically installed the package that you don't want:**Use [`zsync`](https://help.ubuntu.com/community/ZsyncCdImage) to speed up repeated image downloads and to ensure automatic integrity checking.** Pro tip: copy an existing image and rename it to the name of a different image you want and run `zsync` on the different image and it will speed things up there, too.
* Install `apt-rdepends`* [Milestone Process](https://wiki.ubuntu.com/MilestoneProcess) - timing for a new Ubuntu release
* Run `apt-rdepends -r --show=Depends the_unwanted_package`. It will show which packages depend on `the_unwanted_package`.[New Release Cycle Process](https://wiki.ubuntu.com/NewReleaseCycleProcess) - getting dailies started and development started after an Ubuntu release
* Run `apt-rdepends -r --show=Recommends the_unwanted_package`. It will show which packages recommend `the_unwanted_package` (Recommended packages are installed by default).[cdimage crontab](http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/etc/crontab) - timing for building of all Ubuntu images (ours usually takes 90 minutes)
* You may have to run the commands several times to see the complete chain of depends / recommends.[status of building Lubuntu images](https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/eoan/lubuntu)
* [Lubuntu image building logs](http://people.canonical.com/~ubuntu-archive/cd-build-logs/lubuntu/)
//Contents of this page originated from the Ubuntu Wiki, all copyright goes to the respective author//