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

Fix English.

parent 1d18d968
......@@ -1061,7 +1061,7 @@ SHA256.
- [[!tails_gitweb config/chroot_local-includes/etc/skel/.gnupg/gpg.conf]]
- [[!tails_gitweb config/chroot_local-includes/usr/share/amnesia/gconf/apps_seahorse.xml]]
- [[!tails_gitweb config/chroot_local-includes/etc/iceweasel/profile/user.js]]
- hkpms [announce](https://lists.riseup.net/www/arc/monkeysphere/2010-12/msg00001.html)
- hkpms [announcement](https://lists.riseup.net/www/arc/monkeysphere/2010-12/msg00001.html)
- [hkpms in the Monkeysphere issue tracker](https://labs.riseup.net/code/issues/2016)
- hkpms is [available in Debian experimental](http://packages.debian.org/source/experimental/msva-perl)
......
......@@ -181,14 +181,14 @@ Update todo and bugs tags:
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
Write the announcement for the release in `news/version_X.Y.mdwn`. Use the
meta directive to set the post title to "Tails X.Y is out" so
that aggregators (such as Planet Debian Derivatives) display a more
catchy title.
Write an announce listing the security bugs affecting the previous
Write an announcement 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
know that they have to upgrade. This announcement 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
......
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