To enable the proposed archive for Ubuntu 16.04 and later use the Software & Updates program and ensure that Pre-released updates (xenial-proposed) is ticked in the Developer Options tab.
To enable the proposed archive for Ubuntu 14.04 use the Software & Updates program and ensure that Pre-release updates (trusty-proposed) is ticked in the Updates tab.
Or you can modify the software sources manually by adding the following line to /etc/apt/sources.list:
deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main multiverse universe
If you are using a port arch such as armhf/arm64/ppc64el you need to add the following line instead :
deb http://ports.ubuntu.com/ubuntu-ports xenial-proposed restricted main multiverse universe
Replace "xenial" with "trusty", "vivid", "utopic", "precise", or "lucid" depending on which release you are on.
It is recommended to enable selective upgrading from -proposed as described in the next section!
Selective upgrading from -proposed
After enabling the -proposed archive as shown above, you can configure apt to allow selective installs of packages from it instead of upgrading all of your packages to the -proposed versions.
Create the file /etc/apt/preferences.d/proposed-updates with this content:
Package: * Pin: release a=xenial-proposed Pin-Priority: 400
With this preference file in place, Update Manager, Synaptic, Aptitude and Apt won't ask for upgrades from the -proposed repositories.
You can test this by simulating an upgrade with apt:
sudo apt-get upgrade -s
If any packages are available for upgrade then the pinning process was set up incorrectly. Make sure you wrote the proper distro name (trusty, precise, etc.).
If you want to see the trusty-proposed packages under the 'Upgradable Packages' listing, run aptitude as follows
sudo aptitude -t xenial-proposed
In aptitude, you should first update the package listings ('u' key), mark any of the packages you want to upgrade ('+' key), and finally install them ('g' key). After this, if you run Aptitude without options again, the rest of trusty-proposed upgradable packages will remain hidden.
Alternatively, you can use apt-get to install a package from -proposed by using
sudo apt-get install packagename/xenial-proposed
This method uses a higher priority to install packages.
If you use another release of Ubuntu, replace xenial by your release name everywhere.
When running proposed it is recommend that you re-enable Apport's bug filing of crash reports. Crashses regarding proposed packages are automatically tagged 'package-from-proposed', so we can distinguish them from other crash reports.
You can enable Apport's reporting of crashes on a stable system by editing /etc/apport/crashdb.conf and changing the following line in the ubuntu section from:
'problem_types': ['Bug', 'Package'],
'problem_types': ['Bug', 'Package', 'Crash'],
To test that Apport is now running, enter the following command to cause a simple crash and generate a crash file in /var/crash:
sh -c 'kill -SEGV $$'
This should notify about the crash and offer you to submit it to Launchpad. Click on 'Report' and verify that the details look complete (package name and version, has a (broken) stack trace, etc.). Please do not actually send it to Launchpad, though, since it is not a genuine bug.
Installation testing using -proposed
Sometimes you may be asked to test a netboot installer image from trusty-proposed. The images may be found here (replace "i386" with your architecture as necessary):
In order to install successfully from these images, you will normally need to tell the installer to fetch its own components from -proposed as well, which is not the default. To do this, add the following boot parameter:
You must make sure that the mirror you are installing from contains packages from -proposed. All official mirrors will do so; if you operate your own mirror or use a site-local mirror, it may need to be modified to pull from -proposed. Make sure that you do not simply use a loopback mount of a CD or DVD image as an installation source; this is one of the cases where such mirrors will not work, since they do not contain the updated kernel packages required by the new installer.
Uploading your hardware profile
To help us track the hardware test coverage, please upload your hardware profile for the system you will run proposed on using the hardware testing tool, found in the System -> Administration menu or with the command checkbox-gtk.
You can see your submitted information at https://launchpad.net/people/+me/+hwdb-submissions
Register your participation
We have set up an improvised way of tracking -proposed archive coverage using the bug tracker in Launchpad (but we are designing a more automated solution). To register your participation please select the appropriate bug for your architecture here and add a comment using the template in the description. Thanks!
Verifying Stable Release Updates (SRU) bugs
For extra points please help us verify the fixes to the proposed updates.
You don't have to be very technical to do this kind of testing, simply read how to perform a Stable Release Update verification, read the Stable Release Update procedure and choose the packages you want to test from the Stable Release Update report.