Commit 40096eba authored by Tails developers's avatar Tails developers
Browse files

Merge branch 'master' of ssh://webmasters.boum.org/~/wiki

parents 3b6bc642 81cdd32c
......@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-04-12 04:25-0600\n"
"POT-Creation-Date: 2011-09-13 03:32-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
......@@ -105,3 +105,44 @@ msgid ""
"Then try to boot again, and append the end of the boot log (or what seems to "
"be relevant to your problem) to your bug report."
msgstr ""
#. type: Title -
#, no-wrap
msgid "No internet access\n"
msgstr ""
#. type: Plain text
msgid ""
"The WhisperBack bug reporting tool (accessed from the Tails desktop) can of "
"course not send the bug report when there is not internet access. The "
"following steps can be used as a work-around (Note that your bug report will "
"not be anonymous unless you take further steps yourself (e.g. using Tor with "
"a throw-away email account)):"
msgstr ""
#. type: Bullet: '1. '
msgid "In Tails, start the bug reporting tool"
msgstr ""
#. type: Bullet: '2. '
msgid "In the bug report window, expand \"technical details to include\""
msgstr ""
#. type: Bullet: '3. '
msgid "Copy everything in the \"debugging info\" box"
msgstr ""
#. type: Bullet: '4. '
msgid "Paste it to another document (using gedit for instance)"
msgstr ""
#. type: Bullet: '5. '
msgid "Save the document on a USB strick"
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"6. Boot into a system with working networking and send the debugging\n"
"info to us.\n"
msgstr ""
......@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-04-12 04:25-0600\n"
"POT-Creation-Date: 2011-09-13 03:32-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
......@@ -105,3 +105,44 @@ msgid ""
"Then try to boot again, and append the end of the boot log (or what seems to "
"be relevant to your problem) to your bug report."
msgstr ""
#. type: Title -
#, no-wrap
msgid "No internet access\n"
msgstr ""
#. type: Plain text
msgid ""
"The WhisperBack bug reporting tool (accessed from the Tails desktop) can of "
"course not send the bug report when there is not internet access. The "
"following steps can be used as a work-around (Note that your bug report will "
"not be anonymous unless you take further steps yourself (e.g. using Tor with "
"a throw-away email account)):"
msgstr ""
#. type: Bullet: '1. '
msgid "In Tails, start the bug reporting tool"
msgstr ""
#. type: Bullet: '2. '
msgid "In the bug report window, expand \"technical details to include\""
msgstr ""
#. type: Bullet: '3. '
msgid "Copy everything in the \"debugging info\" box"
msgstr ""
#. type: Bullet: '4. '
msgid "Paste it to another document (using gedit for instance)"
msgstr ""
#. type: Bullet: '5. '
msgid "Save the document on a USB strick"
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"6. Boot into a system with working networking and send the debugging\n"
"info to us.\n"
msgstr ""
......@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-04-12 04:25-0600\n"
"POT-Creation-Date: 2011-09-13 03:32-0600\n"
"PO-Revision-Date: 2011-03-25 12:39+0100\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
......@@ -123,3 +123,44 @@ msgid ""
msgstr ""
"Ensuite, essayez de redémarrer, et ajoutez la fin du journal de démarrage "
"(ou ce qui semble correspondre à votre problème) à votre rapport de bug."
#. type: Title -
#, no-wrap
msgid "No internet access\n"
msgstr ""
#. type: Plain text
msgid ""
"The WhisperBack bug reporting tool (accessed from the Tails desktop) can of "
"course not send the bug report when there is not internet access. The "
"following steps can be used as a work-around (Note that your bug report will "
"not be anonymous unless you take further steps yourself (e.g. using Tor with "
"a throw-away email account)):"
msgstr ""
#. type: Bullet: '1. '
msgid "In Tails, start the bug reporting tool"
msgstr ""
#. type: Bullet: '2. '
msgid "In the bug report window, expand \"technical details to include\""
msgstr ""
#. type: Bullet: '3. '
msgid "Copy everything in the \"debugging info\" box"
msgstr ""
#. type: Bullet: '4. '
msgid "Paste it to another document (using gedit for instance)"
msgstr ""
#. type: Bullet: '5. '
msgid "Save the document on a USB strick"
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"6. Boot into a system with working networking and send the debugging\n"
"info to us.\n"
msgstr ""
... including:
[[!toc levels=1]]
Coordinate with Debian security updates
=======================================
See [[release_process/Debian_security_updates]].
Update included files
=====================
Website
-------
Merge the `master` branch into the one used to build the release.
### version number
In the branch used to build the release, update the `inc/*` files to
match the *version number* and *date* of the new release. Don't update
`/inc/stable_i386_hash.html` since the hash can't be computed yet.
### design documentation
git grep PENDING wiki/src/contribute/design*
... and remove the `PENDING-FOR-N.M` warnings.
AdBlock patterns
----------------
Patterns are stored in
`config/chroot_local-includes/etc/iceweasel/profile/adblockplus/`.
upgrade i2p
-----------
See [[todo/upgrade i2p]].
Update Changelog
================
./release NEW_VERSION PREVIOUS_RELEASED_TAG
example:
./release 0.3 0.2
This populates the Changelog with the Git log entries.
Now cleanup some parts of it (semi-)automatically:
perl -pi'' -e 's/\A \[ IkiWiki::Plugin::po::change \]\n//' debian/changelog
perl -pi'' -e 's/\A \* updated PO files\n//' debian/changelog
perl -pi'' -e 's/\A \[ 127\.0\.0\.1 \]\n//' debian/changelog
perl -pi'' -e 's/\A \[ amnesia \]\n//' debian/changelog
perl -pi'' -e 's/\A \[ anonym \]\n//' debian/changelog
perl -pi'' -e 's/\A \[ T\(A\)ILS developers \]\n//' debian/changelog
perl -pi'' -e 's/\A \[ Tails developers \]\n//' debian/changelog
perl -pi'' -e 's/\A \* Added a comment\n//' debian/changelog
perl -pi'' -e 's/\A \* Added a comment:.*\n//' debian/changelog
perl -pi'' -e 's/\A \* todo\+\+\n//i' debian/changelog
perl -pi'' -e 's/\A \* todo--\n//i' debian/changelog
... then launch an editor for the needed cleanup of the result.
Build images
============
[[Build images|build]] and carefully read the build logs to make sure
nothing bad happened.
image size
----------
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.
See [[todo/improve_boot_time_on_cd]] for details.
Testing
=======
Until [[todo/automated_builds_and_tests]] are setup, some minimal, manual testing
has to be done by the person doing the release, in addition to the
real-world tests done by fellow beta-testers.
The manual testing process [[is documented on a dedicated
page|release_process/test]] in order not to clutter this one too much.
Tag the release in Git
======================
git tag -u BE2CD9C1 -m "tagging version ${NEW_VERSION}" "${NEW_VERSION}"
Generate the Torrents
=====================
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
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.
gpg --armor --default-key BE2CD9C1 --detach-sign *.iso
ls --color=never -1 *.asc | while read asc ; do mv $asc ${asc%%.asc}.pgp ; done
Fourth, create a `.torrent` file for every directory to be published:
mktorrent -a \
'https://www.les-renseignements-genereux.org/tracker/announce,http://z6gw6skubmo2pj43.onion:8080/announce' \
<DIRECTORY>
Fifth, check the generated `.torrent` files metainfo, e.g.
using `btshowmetainfo`, to make sure they don't contain
unwanted information.
Sixth, generate detached GnuPG signatures for every published
`.torrent` file:
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.
Upload images
=============
## Upload to HTTP mirrors
- upload
- make sure every webserver listed in the `dl.amnesia.boum.org` round
robin pool has the new version
- test downloading
## Announce, seed and test the Torrents
Announce and seed the Torrents using whatever box you can.
A decent, stable and permanent Internet connexion is required.
Test them with a BitTorrent client running in a different place.
Update the website and Git repository
=====================================
Rename the `.packages` file to remove the `.iso` part of its name.
Copy the `.iso.pgp`, `.packages`, `.torrent` and `.torrent.pgp`
files to the Git repository's `wiki/src/torrents/files/` directory.
Update the latest version and related information in `inc/*`.
Generate the SHA-256 hash of every image to be released in `inc/*`; e.g.
sha256sum tails-i386-0.7.1.iso | cut -f 1 -d ' ' | tr -d '\n' \
> stable_i386_hash.html
Update todo and bugs tags:
- in `todo/*`: replace `pending` tags with `todo/done` tags
- in `bugs/*`: replace links to `pending` with links to `done` (`[[done]]`)
Update the [[features]] page.
Write the announce for the release in `news/version_X.Y.mdwn`. Use the
meta directive to set the post title to "Tails X.Y was released" so
that aggregators (such as Planet Debian Derivatives) display a more
catchy title.
Write an announce listing the security bugs affecting the previous
version in `security/` in order to let the users of the old versions
know that they have to upgrade. This announce page shall be dated back
to a few days before the one to be released was *built*.
Then add the updated `debian/changelog` and you should be ready to
record the last commit before tagging happens:
git commit -m "releasing version ${NEW_VERSION}"
Go wild!
========
Push the last commits and the release tag to our Git repository:
git push --tags
pBYawL http://2hCDm9pFsaeSsWWd.net
......@@ -5,6 +5,9 @@ Monster](https://addons.mozilla.org/fr/firefox/addon/4703/) seems much
better than CS Lite, aka. maintained and nicer UI; it's been uploaded
to Debian recently ([[!debbug 623970]]). Let's switch to it.
> Branch `feature/cookie-monster` installs Cookie Monster instead of
> CS Lite. Now needs to be built, tested, and likely configured.
[[!tag todo/code]]
If in the end we want to keep CS Lite, we should package this one or
......
Markdown is supported
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