Merge remote-tracking branch 'origin/devel' into feature/6342-update-camouflage-for-gnome3
First stab at making the new NetworkManager configuration directory persistent, when the old one was.
adding test report for Tails 1.1~beta1
update tickets
Actually run "Upgrade from ISO" from a USB drive running the old version.

That's what users do, and is buggy. If one already has an up-to-date Tails USB
stick, they can "Clone and upgrade", and won't bother using an ISO image.

Still, let's keep the "Clone from ISO while running the new version" test,
as it tests the Installer in the tested (new) version of Tails, which makes
little sense wrt. what users will do when the new version is out, but may catch
bugs that will affect upgrades to N+1.
Include the syslinux binary, and its MBR, in the ISO filesystem.

This in turn allows Tails Installer to use this binary and MBR, which is
critical for avoiding problems (such as #7345) on "Upgrade from ISO".
Merge branch 'master' of git://git.tails.boum.org/tails
Merge branch 'testing' into bugfix/7345-upgrade-from-iso-from-1.0-to-1.1
Update a bit the USB installation design doc.
Merge remote-tracking branch 'origin/master' into bugfix/7345-upgrade-from-iso-from-1.0-to-1.1
Design doc update: we now upgrade the MBR too.
Rephrase.
Document that newer tails-create-iuk also stores the EFI and syslinux directories in boot.tar.bz2.
Grant additional permissions needed by the tails-install-iuk user.
Update design doc wrt. upgrading syslinux+MBR after full and incremental upgrades.
Agenda++
Fix category
Add speaker's name.
Release process++.
We now depend on Test::BDD::Cucumber 0.16 or later.

... that is now waiting in the backports NEW queue. Likely it'll be accepted by
the time when someone running Wheezy needs to follow these steps.