Commit b3e216b6 authored by Tails developers's avatar Tails developers
Browse files

Improve release and test procedures.

parent 290582f3
......@@ -81,8 +81,8 @@ Check the image size has not changed much since the last release.
SquashFS files order
--------------------
Build ISO images, profile them and update `squashfs.order` in the Git
repository. Then rebuild images.
Build an ISO image, profile it **on bare metal** and update
`squashfs.order` in the Git repository. Then rebuild images.
See [[todo/improve_boot_time_on_cd]] for details.
......@@ -108,14 +108,14 @@ First, create a directory with a suitable name for every image to be
released, such as `tails-i386-0.7`.
Second, copy the built images to these brand new directories and
rename it to fit our `tails-ARCH-DEBIAN_CODENAME-VERSION.iso` naming
rename it to fit our `tails-ARCH-VERSION.iso` naming
convention e.g.:
mv tails-i386-squeeze-0.7-20110303.iso \
tails-i386-0.7.iso
Third, generate detached GnuPG signatures for every published image,
in the same directory as the image and with a .pgp extension; e.g.
in the same directory as the image and with a `.pgp` extension; e.g.
gpg --armor --default-key BE2CD9C1 --detach-sign *.iso
ls --color=never -1 *.asc | while read asc ; do mv $asc ${asc%%.asc}.pgp ; done
......@@ -135,9 +135,7 @@ Sixth, generate detached GnuPG signatures for every published
gpg --armor --default-key BE2CD9C1 --detach-sign \
tails-i386-0.7.torrent
FIXME: mv the .torrent detached signature to have the .pgp extension
as well.
ls --color=never -1 *.asc | while read asc ; do mv $asc ${asc%%.asc}.pgp ; done
Upload images
=============
......
......@@ -168,8 +168,8 @@ steps that are worth [[a dedicated page|test/erase_memory_on_shutdown]].
in working state.
* Doing an apt-get update and installing random packages.
* Boot on bare-metal on USB and CD.
* Boot and check basic functionality is working for every supported language.
* Boot and check basic functionality is working for every supported
language. The virtual keyboard must work and be auto-configured to
use the same keyboard layout as the X session.
* Try to start with the `truecrypt` option on boot, see if it can be found in
the Application -> Accessories menu and that it runs correctly
* Virtual keyboard must work and be auto-configured to use the same
keyboard layout as the X session.
......@@ -14,7 +14,7 @@ minimal system so that it doesn't fill the RAM to boot.
To be able to grep /dev/mem, it must have a kernel with CONFIG_STRICT_DEVMEM
disabled. It is enabled in debian since 2.6.28-1, so we use lenny:
lb config --architecture i386 --linux-flavours 686 --apt-recommends false --distribution lenny --binary-images usb-hdd --binary-indices false --memtest none --packages-lists="minimal" --syslinux-menu vesamenu --initramfs=live-initramfs
lb config --architecture i386 --linux-flavours 686 --apt-recommends false --distribution lenny --binary-images usb-hdd --binary-indices false --memtest none --packages-lists="minimal" --syslinux-menu vesamenu --initramfs=live-initramfs --bootappend-live "init=/bin/bash"
Then install this image on a 2nd USB stick
......@@ -23,9 +23,9 @@ Then install this image on a 2nd USB stick
* boot on Tails
* add `fillram.py` which contains:
string=""
while True:
string = string + "wipe_didnt_work\n"
string=""
while True:
string = string + "wipe_didnt_work\n"
* launch it a few times in parallel (on a 32-bit architecture the
address space of a given process is usually limited at 3 GiB - or
......@@ -35,13 +35,12 @@ Then install this image on a 2nd USB stick
# 2. test that you can get the pattern
* plug the USB stick containing the minimal lenny live system
* plug the USB stick containing the minimal Lenny Live system
* reboot from Tails using SysRq + B
* under syslinux, append `init=/bin/bash` to the kernel commandline in order to
run the test in the initramfs
* actually do the test:
* boot on the minimal Lenny Live system
* actually run the test:
grep -c wipe_didnt_work /dev/mem
grep -c wipe_didnt_work /dev/mem
- you should get some integer larger than zero if the pattern was found in
RAM, which is the expected result ;
......@@ -53,14 +52,14 @@ Then install this image on a 2nd USB stick
* redo step 1
* reboot from Tails the recommanded way : system > reboot
* plug the USB stick containing the minimal lenny live system
* when Tails displays that you can remove the USB stick, remove Tails and
plug the USB stick containing the minimal lenny live system
* under syslinux, append `init=/bin/bash` to the kernel commandline in order to
run the test in the initramfs
* actually do the test:
grep -c wipe_didnt_work /dev/mem
* plug the USB stick containing the minimal Lenny Live system
* when Tails displays that you can remove the USB stick, unplug the
Tails stick and plug the USB stick containing the minimal Lenny Live
system in
* boot on the minimal Lenny Live system
* actually run the test:
grep -c wipe_didnt_work /dev/mem
- you should get zero if the pattern was not found in RAM, which is the
optimal (and expected) result;
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment