Testing

Differences between revisions 163 and 164
Revision 163 as of 2014-10-23 17:42:23
Size: 11622
Editor: phillw
Comment:
Revision 164 as of 2014-10-29 18:47:08
Size: 13144
Editor: wxl
Comment: so much clean up!!!!!!
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
## = Testing Lubuntu =
Line 9: Line 8:
= Testing Lubuntu =
Line 10: Line 10:
== Before Getting Started ==
This section is dedicated to the current development version of Lubuntu. As with all alphas and betas they are not suitable for a production environment, please take the time to read [[http://ubuntuforums.org/showthread.php?t=1594833 | Common Questions for Testing]].
The Testing Team is responsible for using formal test cases to check images of Lubuntu. This allows the [[wxl|Release Manager]] 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.
Line 13: Line 12:
Testing is split into distinct, but joined areas. The '''Daily Builds''', '''Milestone releases''', and '''specific testing.'''
Line 14: Line 14:
To not get overly complicated, think of it as that we have a [[https://wiki.ubuntu.com/Releases | schedule]] to keep to. A few days before a Milestone is due, the daily is plucked and becomes the QA (Quality Assurance) test version for the Milestone release. Once it is confirmed that the QA version works, it then becomes the [[https://wiki.ubuntu.com/Lubuntu/Testing#Milestone_Releases | Milestone]].
Line 15: Line 16:
Whenever you are testing, keep in mind few notes: Meanwhile, daily images should be 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.
Line 17: Line 18:
 1. Make sure to [[https://help.ubuntu.com/community/BackupYourSystem | Backup]] your '''important data'''. 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 [[https://help.ubuntu.com/community/BackupYourSystem | this link]] and [[http://www.howtogeek.com/108869/how-to-back-up-ubuntu-the-easy-way-with-dj-dup/ | this link too]].
 1. You can use [[http://en.wikipedia.org/wiki/Virtual_machine | Virtual Machines]] - for example [[https://help.ubuntu.com/community/VirtualMachines | See this]]. You can use USB Drives or External HDD. You can use your machine. That is totally up to you but please, refer to #1 :)
 1. Using a Development Release is not suitable for daily production machine.
 1. The more you break your installation, the better. That is why, to play it safe, better to use Virtual Machines, Spare Testing Machines and/or USB Drives, specially with Alpha 1 and Alpha 2. Beta Releases are a bit more stable but still under heavy development.
 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. Also, if you have say Alpha 1 installed, it is less helpful to just upgrade it to Alpha 2 or Beta 1. Please, do a fresh new install - you can either [[https://help.ubuntu.com/community/ZsyncCdImage | zsync]] your ISO or download again.
 1. Finally, always remember: '''Better Safe Than Sorry''' :)
All release stages are tracked by [[http://iso.qa.ubuntu.com/ | ISO Tracker]] where you can get the latest builds, see and allocate any [[https://wiki.ubuntu.com/Lubuntu/ReportingBugs | Bugs]].
Line 24: Line 20:
== Start Testing ==
 * '''Lubuntu 14.04 point releases are maintenance releases, do not expect too many changes.'''
== Updates ==
Line 27: Line 22:
 * '''Lubuntu 14.10 is now released.'''  * Ubuntu has dropped the amd64+mac image altogether. If you have an affected machine, just use the amd64 image. If you have troubles, please make sure you have the latest firmware update for your machine and then file a bug if there are still problems.
 * We did not release a ppc image for 14.10 due to various issues. We are going to focus on supporting the architecture for LTS releases. Thus, we need to focus testing in two areas:
   1. Because we plan to include LXQt in the future and we are not sure of Qt support for ppc, daily testing (on release+1) will be essential.
   2. We will encourage ppc users to use LTS versions, so heavy testing should be done on the LTS dailies.
 * There are [[https://blueprints.launchpad.net/ubuntu/+spec/topic-v-flavor-lubuntu|blueprints]] for 15.04. Keep watching there for the official plan and work to do this cycle, which will dictate our focus. The real question is whether or not LXQt will be included or not.
 * There is a [[https://lists.ubuntu.com/archives/lubuntu-users/2014-October/008662.html|prototype of Lubuntu with LXQT]] available. Info and instructions from the boss included. This is only for i386. If you need another architecture, you'll have to build from the lubuntu-dev PPA.
Line 29: Line 29:

== Use old ISOs ==

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' with 'utopic' and use zsync. (You can, of course, simply do a '''mv''', but I like to keep my older iso's handy).

== 14.04 point releases ==

Basically, a point release brings in all the various bug fixes into one 'new' image. To get in to the build they have to pass [[https://wiki.ubuntu.com/StableReleaseUpdates | SRU testing]].

== What will 14.10 bring? ==

Our head of development has stated what is planned for 14.10 and beyond [[https://wiki.ubuntu.com/Lubuntu/Testing/14.10 |here]].


== Why does lubuntu have so many options? ==

As this question does get asked, there is a [[https://wiki.ubuntu.com/Lubuntu/Testing/Why_So_Many_ISOs | page here]] that explains it.
=== Testing Versions ===
 * Lubuntu 14.04 point releases are maintenance releases, do not expect too many changes.
 * Lubuntu 14.10 is now released.
 * Lubuntu 15.04 may include LXQt. Daily images are currently available.
Line 49: Line 36:
 * Please do [[https://wiki.ubuntu.com/Lubuntu/ContactUs#Contact_Us | Join the main mailing lists]] so that you receive information about where lubuntu is heading.  * Please do [[https://wiki.ubuntu.com/Lubuntu/ContactUs#Contact_Us | Join the main mailing lists]] so that you receive information about where Lubuntu is heading.
Line 51: Line 38:
 * '''For Testing Questions''', we ask that you join the [[https://launchpad.net/~lubuntu-qa | lubuntu QA team]] so you can discuss bugs and proposed resolutions.  * '''For Testing Questions''', we ask that you join the [[https://launchpad.net/~lubuntu-qa | lubuntu QA team]] so you can discuss bugs and proposed resolutions. You may also try the more general #ubuntu-quality or the often-offtopic #lubuntu-offtopic on Freenode IRC, but the mailing list is recommended.
Line 53: Line 40:
 * Always ask if you are in doubt :)
 
== Daily Builds ==
Line 56: Line 42:
== Bugs == These iso's are automatically generated every 24 hours using the latest updates on the system from the devs. They are available from [[http://iso.qa.ubuntu.com/|ISO tracker]]. 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 when pre-milestone testing is being carried out (see below).
Line 58: Line 44:
Within bugs related to lubuntu, you will see bugs raised by, or allocated to '''Julien Lavergne'''. Please feel free to add to the comments but do '''NOT''' alter the status of these bugs as they are being dealt with by our head of development in readiness for the fix being released. == Milestone releases ==
Line 60: Line 46:
Please head over to '''[[https://wiki.ubuntu.com/QATeam/Overview/#Bugs | All about bugs]]''' for further information on how bug reporting works and why it is so important. Alpha, Beta and Final (formerly known as Release Candidates (RC)) are also tested using [[http://iso.qa.ubuntu.com/|ISO tracker]]. If you want to help out in this important area of testing, please read through [[https://wiki.ubuntu.com/Testing/ISO/Procedures | Procedures]] for further details. These appear a couple of days before the actual Milestone release so that we can check they are okay to become Milestone releases.
Line 62: Line 48:

== Testing ==
Testing is split into distinct, but joined areas. The '''Daily Builds''', the '''QA-testing of Milestone releases''' and the '''Milestone releases''' themselves.

To not get overly complicated, think of it as that we have a [[https://wiki.ubuntu.com/UtopicUnicorn/ReleaseSchedule | schedule]] to keep to. A few days before a Milestone is due, the daily is plucked and becomes the QA (Quality Assurance) test version for the Milestone release. Once it is confirmed that the QA version works, it then becomes the [[https://wiki.ubuntu.com/Lubuntu/Testing#Milestone_Releases | Milestone]].

All release stages are tracked by [[http://iso.qa.ubuntu.com/ | ISO Tracker]] where you can get the latest builds, see and allocate any [[https://wiki.ubuntu.com/Lubuntu/ReportingBugs | Bugs]].

So, in order of how they happen.

=== Daily Builds ===

These iso's are automatically generated every 24 hours using the latest updates on the system from the devs. They are available from [[http://iso.qa.ubuntu.com/|ISO tracker]]. Using the [[https://help.ubuntu.com/community/ZsyncCdImage | zsync (or rsync)]] option allows you to update your [[https://help.ubuntu.com/community/BurningIsoHowto |iso]] to any of the various dailies you choose to follow without having to re-download the entire iso. 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 when pre-milestone testing is being carried out (see below).

=== When they build ===

The Alternates take approximately 30 - 45 minutes to complete.
The Desktops take approximately 90 minutes to complete.

==== 14.04 ====

Timed to start at 15:29 UTC

==== 14.10 ====

Timed to start at 16:29 UTC

Please note from the release team: ''Sure, as long as it's clear that it's subject to change - We're not intending to make any promises here. We won't change them around frivolously or anything but it's possible.''

The timing of the auto build of lubuntu can be found [[http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/etc/crontab | here ]]. If you do notice that builds are not appearing as expected, please contact [[wxl]] to let him know.

=== QA testing of Milestone releases ===

Alpha, Beta and Release Candidates (RC) are also tested using [[http://iso.qa.ubuntu.com/|ISO tracker]]. If you want to help out in this important area of testing, please read through [[https://wiki.ubuntu.com/Testing/ISO/Procedures | Procedures]] for further details. These appear a couple of days before the actual Milestone release so that we can check they are okay to become Milestone releases.

'''QA testing is to ensure the actual install iso works, if you can, please get involved in the qa testing'''

==== Rebuilding a Release Candidate ====

These are carried out manually, during this time the release team do update the [[http://iso.qa.ubuntu.com/qatracker | notice panel]]. Please ask on #ubuntu-release if you have questions.

=== Milestone Releases ===
QA testing is to ensure the actual released install iso works, if you can, please get involved in the qa testing.
Line 109: Line 52:
Note this also includes point releases on LTS versions. Basically, a point release brings in all the various bug fixes into one 'new' image. To get in to the build they have to pass [[https://wiki.ubuntu.com/StableReleaseUpdates | SRU testing]].
Line 111: Line 56:

== General Testing ==
During the release cycle, things will get broken. You can really reduce these occurrences by taking the time to read [[http://ubuntuforums.org/showthread.php?t=1479146|Partial Upgrades]].

=== Known Issues ===
All the known issues for a particular release are mentioned in the Announcement email, and are available to see at [[http://iso.qa.ubuntu.com/ | ISO Tracker]].

=== Manual test of ISO and CD ===
On the help-pages of Ubuntu there is an extensive guide on [[https://help.ubuntu.com/community/HowToMD5SUM|how to MD5SUM]]. In our case the terminal would be [[https://wiki.ubuntu.com/Lubuntu/DocumentationHelp/LXTerminal| LXTerminal]].

=== PPC and Intel Macs ===

There is now an area for [[https://wiki.ubuntu.com/Lubuntu/Testing/PPC%26Mac64 | Power PCs and Intel Macs]]. Please do join to help lubuntu have a release for that system.

 
Line 129: Line 59:
You can do more specific tests, like ones done for the Ubuntu ISO : http://iso.qa.ubuntu.com/qatracker/test/5090 You can do [[http://iso.qa.ubuntu.com/qatracker/test/5090|more specific tests]], like ones done for the Ubuntu ISO.
Line 152: Line 82:
=== PPA Testing ===
Sometimes during the test cycle one of the developers may ask you to test something specific for them, or their team. For more details of this important area, head over to [[https://wiki.ubuntu.com/Lubuntu/Testing/PPA_Testing | PPA testing ]]

There are now packages for LXDE components built from upstream git, and re-built when a new revision is committed. It's hosted on the daily build PPA for [[https://launchpad.net/~lubuntu-dev/+archive/lubuntu-daily | Lubuntu-dev]], packages for currently supported releases plus the development release are available. If you are working on a Lubuntu bug, please do test with these ppa areas to check if it has been fixed upstream.

Bugs against LXQt should be filed on the [[https://github.com/lxde/lxde-qt|upstream git]] if you're sure it's an LXQt problem, otherwise file against [[https://launchpad.net/lubuntu-next|lubuntu-next on Launchpad]].

== General Information ==

=== Before you get started ===

This section is dedicated to the current development version of Lubuntu. As with all alphas and betas they are not suitable for a production environment, please take the time to read [[http://ubuntuforums.org/showthread.php?t=1594833 | Common Questions for Testing]].

Whenever you are testing, keep in mind few notes:

 1. Make sure to [[https://help.ubuntu.com/community/BackupYourSystem | Backup]] your '''important data'''. 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 [[https://help.ubuntu.com/community/BackupYourSystem | this link]] and [[http://www.howtogeek.com/108869/how-to-back-up-ubuntu-the-easy-way-with-dj-dup/ | this link too]].
 1. You can use [[http://en.wikipedia.org/wiki/Virtual_machine | Virtual Machines]] - for example [[https://help.ubuntu.com/community/VirtualMachines | See this]]. You can use USB Drives or External HDD. You can use your machine. That is totally up to you but please, refer to #1 :)
 1. Using a Development Release is not suitable for daily production machine.
 1. The more you break your installation, the better. That is why, to play it safe, better to use Virtual Machines, Spare Testing Machines and/or USB Drives, specially with Alpha 1 and Alpha 2. Beta Releases are a bit more stable but still under heavy development.
 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. Also, if you have say Alpha 1 installed, it is less helpful to just upgrade it to Alpha 2 or Beta 1. Please, do a fresh new install - you can either [[https://help.ubuntu.com/community/ZsyncCdImage | zsync]] your ISO or download again.
 1. Finally, always remember: '''Better Safe Than Sorry''' :)
 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' with 'utopic' and use [[https://help.ubuntu.com/community/ZsyncCdImage| zsync]].

=== Why does lubuntu have so many images? ===

As this question does get asked, there is a [[https://wiki.ubuntu.com/Lubuntu/Testing/Why_So_Many_ISOs | page here]] that explains it.

==== When images build ====

The Alternates take approximately 30 - 45 minutes to complete.
The Desktops take approximately 90 minutes to complete.

Please note from the release team: ''Sure, as long as it's clear that it's subject to change - We're not intending to make any promises here. We won't change them around frivolously or anything but it's possible.''

The timing of the auto build of lubuntu can be found [[http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/etc/crontab | here ]]. If you do notice that builds are not appearing as expected, please contact [[wxl]] and let him know.

==== Rebuilding a Release Candidate ====

These are carried out manually, during this time the release team do update the [[http://iso.qa.ubuntu.com/qatracker | notice panel]]. Please ask on #ubuntu-release if you have questions.

=== Bugs ===

Within bugs related to lubuntu, you will see bugs raised by, or allocated to '''Julien Lavergne'''. Please feel free to add to the comments but do '''NOT''' alter the status of these bugs as they are being dealt with by our head of development in readiness for the fix being released.

Please head over to '''[[https://wiki.ubuntu.com/QATeam/Overview/#Bugs | All about bugs]]''' for further information on how bug reporting works and why it is so important.

=== Partial Upgrades ===
During the release cycle, things will get broken. You can really reduce these occurrences by taking the time to read [[http://ubuntuforums.org/showthread.php?t=1479146|Partial Upgrades]].

=== Known Issues ===
All the known issues for a particular release are mentioned in the Announcement email, and are available to see at [[http://iso.qa.ubuntu.com/ | ISO Tracker]].

=== Manual test of ISO and CD ===
On the help-pages of Ubuntu there is an extensive guide on [[https://help.ubuntu.com/community/HowToMD5SUM|how to MD5SUM]]. In our case the terminal would be [[https://wiki.ubuntu.com/Lubuntu/DocumentationHelp/LXTerminal| LXTerminal]].

=== PPC ===

Except for Ubuntu Server, Lubuntu is the only flavor supporting [[https://wiki.ubuntu.com/Lubuntu/Testing/PPC%26Mac64 | Power PCs]]. Please do join to help Lubuntu have a release for that system.
Line 159: Line 148:
=== PPA Testing ===
Sometimes during the test cycle one of the developers may ask you to test something specific for them, or their team. For more details of this important area, head over to [[https://wiki.ubuntu.com/Lubuntu/Testing/PPA_Testing | PPA testing ]]

=== LXDE PPA ===

There are now packages for LXDE components built from upstream git, and re-built when a new revision is committed. It's hosted on the daily build PPA for [[https://launchpad.net/~lubuntu-dev/+archive/lubuntu-daily | Lubuntu-dev]], packages for currently supported releases plus the development release are available. If you are working on a lubuntu bug, please do test with these ppa areas to check if it has been fixed upstream.

The use of this ppa is as per the above section.

= Other tools =
=== Other tools ===

Testing Lubuntu

The Testing Team is responsible for using formal test cases to check images of Lubuntu. This allows the Release Manager 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.

Testing is split into distinct, but joined areas. The Daily Builds, Milestone releases, and specific testing.

To not get overly complicated, think of it as that we have a schedule to keep to. A few days before a Milestone is due, the daily is plucked and becomes the QA (Quality Assurance) test version for the Milestone release. Once it is confirmed that the QA version works, it then becomes the Milestone.

Meanwhile, daily images should be 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.

All release stages are tracked by ISO Tracker where you can get the latest builds, see and allocate any Bugs.

Updates

  • Ubuntu has dropped the amd64+mac image altogether. If you have an affected machine, just use the amd64 image. If you have troubles, please make sure you have the latest firmware update for your machine and then file a bug if there are still problems.
  • We did not release a ppc image for 14.10 due to various issues. We are going to focus on supporting the architecture for LTS releases. Thus, we need to focus testing in two areas:
    1. Because we plan to include LXQt in the future and we are not sure of Qt support for ppc, daily testing (on release+1) will be essential.
    2. We will encourage ppc users to use LTS versions, so heavy testing should be done on the LTS dailies.
  • There are blueprints for 15.04. Keep watching there for the official plan and work to do this cycle, which will dictate our focus. The real question is whether or not LXQt will be included or not.

  • There is a prototype of Lubuntu with LXQT available. Info and instructions from the boss included. This is only for i386. If you need another architecture, you'll have to build from the lubuntu-dev PPA.

Testing Versions

  • Lubuntu 14.04 point releases are maintenance releases, do not expect too many changes.
  • Lubuntu 14.10 is now released.
  • Lubuntu 15.04 may include LXQt. Daily images are currently available.

Getting Involved

  • Please do Join the main mailing lists so that you receive information about where Lubuntu is heading.

  • For Testing Questions, we ask that you join the lubuntu QA team so you can discuss bugs and proposed resolutions. You may also try the more general #ubuntu-quality or the often-offtopic #lubuntu-offtopic on Freenode IRC, but the mailing list is recommended.

Daily Builds

These iso's are automatically generated every 24 hours using the latest updates on the system from the devs. They are available from ISO tracker. 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 when pre-milestone testing is being carried out (see below).

Milestone releases

Alpha, Beta and Final (formerly known as Release Candidates (RC)) are also tested using ISO tracker. If you want to help out in this important area of testing, please read through Procedures for further details. These appear a couple of days before the actual Milestone release so that we can check they are okay to become Milestone releases.

QA testing is to ensure the actual released install iso works, if you can, please get involved in the qa testing.

Once a Milestone release passes the QA testing, it becomes a Milestone Release and is listed on the Releases as such.

Note this also includes point releases on LTS versions. Basically, a point release brings in all the various bug fixes into one 'new' image. To get in to the build they have to pass SRU testing.

If you would to know more about how this all works, have a read of Stages of testing.

Specific Testing

QA tests

You can do more specific tests, like ones done for the Ubuntu ISO.

Laptop Testing

Laptops never cease to have their little 'quirks'. You can help on this important area by heading over to Laptop Testing for full details.

Applications test cases

You can also test specific programs :

Performance tests

You can test some aspects of Lubuntu performance with the following programs :

PPA Testing

Sometimes during the test cycle one of the developers may ask you to test something specific for them, or their team. For more details of this important area, head over to PPA testing

There are now packages for LXDE components built from upstream git, and re-built when a new revision is committed. It's hosted on the daily build PPA for Lubuntu-dev, packages for currently supported releases plus the development release are available. If you are working on a Lubuntu bug, please do test with these ppa areas to check if it has been fixed upstream.

Bugs against LXQt should be filed on the upstream git if you're sure it's an LXQt problem, otherwise file against lubuntu-next on Launchpad.

General Information

Before you get started

This section is dedicated to the current development version of Lubuntu. As with all alphas and betas they are not suitable for a production environment, please take the time to read Common Questions for Testing.

Whenever you are testing, keep in mind few notes:

  1. Make sure to Backup your important data. 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 and this link too.

  2. You can use Virtual Machines - for example See this. You can use USB Drives or External HDD. You can use your machine. That is totally up to you but please, refer to #1 Smile :)

  3. Using a Development Release is not suitable for daily production machine.
  4. The more you break your installation, the better. That is why, to play it safe, better to use Virtual Machines, Spare Testing Machines and/or USB Drives, specially with Alpha 1 and Alpha 2. Beta Releases are a bit more stable but still under heavy development.
  5. 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, if you have say Alpha 1 installed, it is less helpful to just upgrade it to Alpha 2 or Beta 1. Please, do a fresh new install - you can either zsync your ISO or download again.

  6. Finally, always remember: Better Safe Than Sorry Smile :)

  7. 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' with 'utopic' and use zsync.

Why does lubuntu have so many images?

As this question does get asked, there is a page here that explains it.

When images build

The Alternates take approximately 30 - 45 minutes to complete. The Desktops take approximately 90 minutes to complete.

Please note from the release team: Sure, as long as it's clear that it's subject to change - We're not intending to make any promises here. We won't change them around frivolously or anything but it's possible.

The timing of the auto build of lubuntu can be found here. If you do notice that builds are not appearing as expected, please contact wxl and let him know.

Rebuilding a Release Candidate

These are carried out manually, during this time the release team do update the notice panel. Please ask on #ubuntu-release if you have questions.

Bugs

Within bugs related to lubuntu, you will see bugs raised by, or allocated to Julien Lavergne. Please feel free to add to the comments but do NOT alter the status of these bugs as they are being dealt with by our head of development in readiness for the fix being released.

Please head over to All about bugs for further information on how bug reporting works and why it is so important.

Partial Upgrades

During the release cycle, things will get broken. You can really reduce these occurrences by taking the time to read Partial Upgrades.

Known Issues

All the known issues for a particular release are mentioned in the Announcement email, and are available to see at ISO Tracker.

Manual test of ISO and CD

On the help-pages of Ubuntu there is an extensive guide on how to MD5SUM. In our case the terminal would be LXTerminal.

PPC

Except for Ubuntu Server, Lubuntu is the only flavor supporting Power PCs. Please do join to help Lubuntu have a release for that system.

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 :

  • Install apt-rdepends
  • run "apt-rdepends -r --show=Depends the_unwanted_package" => It will show which packages depend on the_unwanted_package.

  • run "apt-rdepends -r --show=Recommends the_unwanted_package" => It will show which packages recommend the_package_unwanted (Recommended packages are installed by default).

  • You may have to run the commands several times to see the complete chain of depends / recommends.

Other tools

Jenkins runs automated tests. In particular, there's one that deals with Ubiquity that would be a good way to see if we're having problems with the Desktop ISO.

Lubuntu/Testing (last edited 2018-01-15 04:06:43 by tsimonq2)