Commit e2464f79 authored by Ulrike Uhlig's avatar Ulrike Uhlig
Browse files

Merge branch 'master' of webmasters.boum.org:wiki

parents be3230e3 6e6389c4
......@@ -328,11 +328,11 @@ just appeared:
After a new Tails release is out
--------------------------------
If you just put out a final release:
### If you just put out a final release
* [[merge `stable` or `testing` into
`devel`|APT_repository/custom#workflow-merge-main-branch]]
* increment the version number in devel's `debian/changelog` to match
* increment the version number in `devel`'s `debian/changelog` to match
the next major release, so that
next builds from the `devel` branch do not use the APT suite meant
for the last release:
......@@ -356,20 +356,6 @@ If you just put out a final release:
git commit debian/changelog \
-m "Add dummy changelog entry for ${NEXT_PLANNED_MINOR_VERSION:?}."
If you just released a RC (XXX: please automate these steps during the
3.2~rc1 release process, based on the above commands):
* add a dummy changelog entry (for the upcoming, non-RC version) in
the branch used for the release (`stable` or `testing`), so that the
next builds from it do not use the APT suite meant for the RC
* add a dummy changelog entry (for the release *after* the one you
released a RC for) in the branch used for the release (`stable` or
`testing`), so that the next builds from it do not use the APT suite
meant for the RC (XXX: I don't understand what this is about; is it
instead about adding an entry for that release on the `devel`
branch? -- intrigeri)
If the release was a major one, then:
1. [[Hard reset the stable APT suite to
......@@ -382,6 +368,30 @@ If the release was a major one, then:
git commit config/APT_overlays.d/ \
-m "Empty the list of APT overlays: they were merged"
### Else, if you just released a RC
* increment the version number in `debian/changelog` on the branch
used for the release, to match the upcoming non-RC release, so that
the next builds from it do not use the APT suite meant for the RC:
cd "${RELEASE_CHECKOUT}" && \
git checkout "${RELEASE_BRANCH:?}" && \
dch --newversion "${NEXT_PLANNED_MAJOR_VERSION:?}" \
"Dummy entry for next release." && \
git commit debian/changelog \
-m "Add dummy changelog entry for ${NEXT_PLANNED_MAJOR_VERSION:?}."
* increment the version number in `devel`'s `debian/changelog` to
match the second next major release, so that images built from there
have the right version number:
cd "${RELEASE_CHECKOUT}" && \
git checkout devel && \
dch --newversion "${SECOND_NEXT_PLANNED_MAJOR_VERSION:?}" \
"Dummy entry for next release." && \
git commit debian/changelog \
-m "Add dummy changelog entry for ${SECOND_NEXT_PLANNED_MAJOR_VERSION:?}."
Giving access to a core developer
---------------------------------
......
......@@ -4,10 +4,6 @@ All times are referenced to Berlin and Paris time.
## 2018Q3
* 2018-08-16: Build and upload tentative 3.9~rc1 ISO image — intrigeri
* 2018-08-17: Test and release 3.9~rc1 — intrigeri
* 2018-09-03, 19:00: [[Contributors meeting|contribute/meetings]]
* 2018-09-04: Build and upload tentative 3.9 ISO image — intrigeri
......@@ -19,17 +15,17 @@ All times are referenced to Berlin and Paris time.
* 2018-10-03, 19:00: [[Contributors meeting|contribute/meetings]]
* 2018-10-23: **Release 3.10** (Firefox 60.3, bugfix release) — anonym is the RM
* 2018-10-23: **Release 3.10** (Firefox 60.3, bugfix release)
* 2018-11-06, 19:00: [[Contributors meeting|contribute/meetings]]
* 2018-12-03, 19:00: [[Contributors meeting|contribute/meetings]]
* 2018-12-11: **Release 3.11** (Firefox 60.4, major release) — anonym is the RM
* 2018-12-11: **Release 3.11** (Firefox 60.4, bugfix release)
## 2019Q1
* 2019-01-29: **Release 3.12** (Firefox 60.5)
* 2019-01-29: **Release 3.12** (Firefox 60.5, major release)
* 2019-03-19: **Release 3.13** (Firefox 60.6)
......
......@@ -40,7 +40,14 @@ the scripts snippets found on this page:
* `NEXT_PLANNED_VERSION`: set to the version number of the next Tails release
(e.g. 0.23 when releasing 0.22.1, and 1.3 when releasing 1.2)
* `NEXT_PLANNED_MAJOR_VERSION`: set to the version number of the next
*major* Tails release
*major* Tails release; if you're preparing a RC for a major release,
use that major release; otherwise, use whatever the next planned
major release is
* `SECOND_NEXT_PLANNED_MAJOR_VERSION`: set to the version number of
the second next *major* Tails release; e.g. if preparing the RC for
the 3.9 major release, then set this to 3.12 (3.9 is the next major
release, 3.10 and 3.11 are bugfix releases, 3.12 is a major
release).
* `NEXT_PLANNED_MINOR_VERSION`: set to the version number of the next
*minor* Tails release; if the next release is a point-release, use
that one; otherwise, use `${VERSION}.1`
......@@ -1134,14 +1141,14 @@ If preparing a release candidate
Skip this part if preparing a final release.
Copy the `.iso.sig` file into the website repository:
Copy the signature and the Torrent into the website repository:
cp "${ISO_PATH:?}.sig" \
"${ISOS:?}/tails-amd64-${VERSION:?}.torrent" \
"${MASTER_CHECKOUT:?}/wiki/src/torrents/files/"
"${RELEASE_CHECKOUT:?}/wiki/src/torrents/files/"
Write the announcement for the release in
`${MASTER_CHECKOUT:?}/wiki/src/news/test_${TAG:?}.mdwn`, including:
`${RELEASE_CHECKOUT:?}/wiki/src/news/test_${TAG:?}.mdwn`, including:
- Update the `meta title` directive.
- Update the `meta date` directive.
......@@ -1159,10 +1166,6 @@ Write the announcement for the release in
In any case
-----------
If preparing a final release, what follows happens on the
`$WEBSITE_RELEASE_BRANCH` in `$RELEASE_CHECKOUT`. Else, it happens in
`$MASTER_CHECKOUT`.
Generate PO files for the announcements and record the last commit
before putting the release out for real:
......@@ -1204,8 +1207,8 @@ Push
### Git
If preparing an actual release, push the last commits to our Git
repository and put `master` in the following state:
Push the last commits to our Git repository and put `master` in the
following state:
( cd "${RELEASE_CHECKOUT:?}" && \
git push origin \
......@@ -1214,12 +1217,8 @@ repository and put `master` in the following state:
) && \
( cd "${MASTER_CHECKOUT:?}" && \
git fetch && \
git merge "origin/${WEBSITE_RELEASE_BRANCH:?}" \
)
In any case, ensure that `master` has `stable` as its base branch:
( cd "${MASTER_CHECKOUT:?}" && \
git merge origin/master && \
git merge "origin/${WEBSITE_RELEASE_BRANCH:?}" && \
echo "stable" > config/base_branch && \
git commit config/base_branch \
-m "Restore master's base branch." \
......@@ -1347,14 +1346,6 @@ We announce *major* releases on the Tor blog:
- click *Preview* and ensure everything is OK
- click *Save and publish*
Tor weekly news
---------------
Write a short announcement for the [Tor weekly
news](https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews)'s
next issue (follow the *Next steps* link), or find someone who's happy
to do it.
Amnesia news
------------
......@@ -1380,14 +1371,14 @@ this, and skip what does not make sense for a RC.
`ssh bittorrent.lizard transmission-remote -t "${PREVIOUS_VERSION_TRANSMISSION_ID:?}" --remove-and-delete`
1. Remove any remaining RC for the just-published release from
the mirrors.
1. Remove IUKs that are more than 6 months old from
1. Remove IUKs that are more than 9 months old from
`/{stable,alpha}/iuk` on the rsync server:
- first check that it's not going to remove anything we want to keep:
ssh rsync.lizard /bin/sh -c \
\"find /srv/rsync/tails/tails/alpha \
/srv/rsync/tails/tails/stable \
-type f -name '*.iuk' -mtime '+183' \
-type f -name '*.iuk' -mtime '+270' \
-not -name '*~test_*~test.iuk' -ls \
\"
......@@ -1396,7 +1387,7 @@ this, and skip what does not make sense for a RC.
ssh rsync.lizard /bin/sh -c \
\"find /srv/rsync/tails/tails/alpha \
/srv/rsync/tails/tails/stable \
-type f -name '*.iuk' -mtime '+183' \
-type f -name '*.iuk' -mtime '+270' \
-not -name '*~test_*~test.iuk' -delete \
\"
......@@ -1443,6 +1434,7 @@ this, and skip what does not make sense for a RC.
appropriately (they should expire after the major release _after_
the one you're preparing). Look carefully at the output of this command:
cd "${RELEASE_CHECKOUT:?}" && \
git checkout "${RELEASE_BRANCH:?}" && \
for dir in config/APT_snapshots.d vagrant/definitions/tails-builder/config/APT_snapshots.d; do
(
......
[[!meta title="Call for testing: 3.9~rc1"]]
[[!meta date="Fri, 17 Aug 2018 16:44:06 +0000"]]
[[!tag announce]]
You can help Tails! The first release candidate for the upcoming
version 3.9 is out. We are very excited and cannot wait to hear what
you think about it :)
[[!toc levels=1]]
# Changes
## Upgrades and changes
- Integrate the _Additional Software Packages_ feature into the desktop
and revamp the interface of "Configure Persistent Volume".
- Support unlocking _TrueCrypt_ and _VeraCrypt_ encrypted volumes
on the desktop.
- Upgrade _Tor Browser_ to 8.0a9, based on Firefox 60 ESR.
- Upgrade _Thunderbird_ to 60.0b10.
- Improve hardware support: upgrade some graphics drivers, firmware,
and upgrade _Linux_ to 4.17.
- Upgrade _tor_ to 0.3.4.6-rc.
- Due to security concerns the _Liferea_ feed reader will be removed
from Tails by the end of 2018. Please migrate your feeds
to Thunderbird.
## Fixed problems
- Don't display the Enigmail configuration wizard in every Tails session.
- Many problems fixed in _Tails Installer_ and elsewhere.
For more details, read our [[!tails_gitweb debian/changelog desc="changelog"]].
Known issues
==============
_Tor Browser_ always prompts whether it should ask webpages in English
This will be fixed in Tails 3.9 ([[!tails_ticket 15706]]).
The first time _Tor Browser_ is started in a given Tails session,
the _NoScript_ icon is not displayed ([[!tor_bug 23359]]). If you
need this icon, restart _Tor Browser_.
This version may be slower than usual to start from DVD.
See the list of [[long-standing issues|support/known_issues]].
# How to test Tails 3.9~rc1?
**Keep in mind that this is a test image**. We tested that it is not
broken in obvious ways, but it might still contain undiscovered
issues.
But test wildly!
If you find anything that is not working as it should, please report to
us on <tails-testers@boum.org>.
Bonus points if you first check if it is a
<a href="#known_issues">known issue of this release</a> or a
[[longstanding known issue|support/known_issues]].
Upgrade from 3.8
----------------
1. Start Tails 3.8 on a USB stick installed using *Tails Installer* and
[[set an administration password|doc/first_steps/startup_options/administration_password]].
1. Run this command in a <span class="application">Terminal</span>
to select the "alpha" upgrade channel and start the upgrade:
echo TAILS_CHANNEL=\"alpha\" | sudo tee -a /etc/os-release && \
tails-upgrade-frontend-wrapper
and enter the administration password when asked for the "password
for amnesia".
1. After the upgrade is installed, restart Tails and choose
<span class="menuchoice">
<span class="guimenu">Applications</span>&nbsp;▸
<span class="guisubmenu">Tails</span>&nbsp;▸
<span class="guimenuitem">About Tails</span>
</span>
to verify that you are running Tails 3.9~rc1.
Download and install
--------------------
You can install 3.9~rc1 by following our usual
[[installation instructions|install]], skipping the **Download and
verify** step.
<a class="download-file use-mirror-pool" href="http://dl.amnesia.boum.org/tails/alpha/tails-amd64-3.9~rc1/tails-amd64-3.9~rc1.iso">Tails 3.9~rc1 ISO image</a>
<span class="openpgp-small-link">[[OpenPGP signature|torrents/files/tails-amd64-3.9~rc1.iso.sig]]</span>
<br/>
<a class="download-file" href="https://tails.boum.org/torrents/files/tails-amd64-3.9~rc1.torrent" >Tails 3.9~rc1 torrent</a>
<a id="known_issues"></a>
# What's coming up?
Tails 3.9 is [[scheduled|contribute/calendar]] for September 5.
Have a look at our [[!tails_roadmap]] to see where we are heading to.
We need your help and there are many ways to [[contribute to
Tails|contribute]] (<a href="https://tails.boum.org/donate?r=3.9-rc1">donating</a> is only one of
them). Come [[talk to us|about/contact#tails-dev]]!
-----BEGIN PGP SIGNATURE-----
iHUEABYKAB0WIQTNTUNRr6aTP1dKmvuQsrS9eu0jXwUCW3XlpAAKCRCQsrS9eu0j
X7ldAQD7cBGLtIrbBN1HlPurgbtoizE40N4DubH69zyvAgcl2wEA/O5cYMU99ITt
Bm2zkvJpz3+LSlRNoTsDX1ZKauvhqgQ=
=GnRA
-----END PGP SIGNATURE-----
---
build-target: amd64
channel: alpha
product-name: Tails
product-version: '3.11'
-----BEGIN PGP SIGNATURE-----
iHUEABYKAB0WIQTNTUNRr6aTP1dKmvuQsrS9eu0jXwUCW3cDQgAKCRCQsrS9eu0j
Xx/uAP4/cn+sGG6Tu0FxjfjF02aAXo0pRMiMe8ZJoXzy4w5lAAEAhEgyRZ4gFElB
/hMGj1a+aT4FMZNKM+cCz3g2Rd7kkAA=
=pNyo
-----END PGP SIGNATURE-----
---
build-target: amd64
channel: stable
product-name: Tails
product-version: '3.11'
-----BEGIN PGP SIGNATURE-----
iHUEABYKAB0WIQTNTUNRr6aTP1dKmvuQsrS9eu0jXwUCW3cDPAAKCRCQsrS9eu0j
X/3rAP92fdTfouSpGrF59ibaGw5YmSLSMKGEgFMiYD0z0ccKmwD6A2WueZCHFcdz
Q9IuoToRQUcnGX7u+racvw7RJ2dApQk=
=n59j
-----END PGP SIGNATURE-----
---
build-target: amd64
channel: alpha
product-name: Tails
product-version: '3.12'
-----BEGIN PGP SIGNATURE-----
iHUEABYKAB0WIQTNTUNRr6aTP1dKmvuQsrS9eu0jXwUCW3cDTAAKCRCQsrS9eu0j
XxknAP4xIS2GdAafE0AjlVEyXm2BpO/5VDwvMTXtRkkz//w5SgEAn+H0Kq8kSeNR
o4cWBv5k1VAC0O3MxJ9q6lV6nYzd9wk=
=ESpR
-----END PGP SIGNATURE-----
---
build-target: amd64
channel: stable
product-name: Tails
product-version: '3.12'
-----BEGIN PGP SIGNATURE-----
iHUEABYKAB0WIQTNTUNRr6aTP1dKmvuQsrS9eu0jXwUCW3cDRwAKCRCQsrS9eu0j
X2ihAP9fC+1AC/9ZlJQFu4hx43/pSqJl6+k6uKt6uBbvDxijkAD6A/NMS+4ywMJz
EE8KEqyxad3N0BwOlCI4EkgTHdSoyQ4=
=3qIl
-----END PGP SIGNATURE-----
......@@ -3,3 +3,18 @@ build-target: amd64
channel: alpha
product-name: Tails
product-version: '3.8'
upgrades:
- details-url: https://tails.boum.org/news/test_3.9-rc1/
type: major
upgrade-paths:
- target-files:
- sha256: 743641f7093e2e597ebef39d14df4678db381aebd2ffe6d518c679fa5d921eb0
size: 1225568256
url: http://dl.amnesia.boum.org/tails/alpha/tails-amd64-3.9~rc1/tails-amd64-3.9~rc1.iso
type: full
- target-files:
- sha256: 2c5baba04429189209c610c5ac32962eb587c00a5da7dae91d379e52299af0b9
size: 376145920
url: http://dl.amnesia.boum.org/tails/alpha/iuk/Tails_amd64_3.8_to_3.9~rc1.iuk
type: incremental
version: 3.9~rc1
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEL6+boNZbs3HwvC1GMCCnqcK3JzMFAlqnLj0ACgkQMCCnqcK3
JzN01w//aQ1Vouk/WJ+sDooFOugnhg/dpbXy23J3pp5WFPUFgXW2aZ0HmE8TEweP
/FR/yF68T4MTW+ScNmVLOoCCsHJc1B2cbjbh1PmC1rCMB5HQpNp5FDaYg/jRgmAf
OYOmrMoLrJwl//RbrjxzkM1AhGF95UP53LViq8kH0kNfL/hKf1a5SgnCGkGWaGfZ
nUhV324BPvs3RM2XMYXj40rwf8+LBQb24HkHPCGohp0XnFidj48p+KiEsbVufFTF
A5YV4r18YFT2eKOfpSkb+b5xejediluH9HvRVXR1hOlwnKOlSr9ypduRJ3TV1cqJ
V8AL6+sjzgh9tBrXYk8mIGv/IbDjweto4iVAq0pHWEdI9SEkBXNCERSVikqeFVfx
uRSjPFU7yf+o6rKC8U6XXV1h23Yv4Ww8sJjJaSTmPjUdskDepX2PGQqTcRmTu55Y
1PQoFKHBSYts/HYHFvHohNFEZDbp9lqjR11GAfAv4rQxPEeDSfUXokBksoeQoUua
Ltd4gbfLBgM//e96x1bRAQ4vlO+SUdN+FlJWmDsXP3Z5yH+OuEHUwNkGEgj1rcUj
SWmEAYOTRSSQcBg03soAltFN9xmJQPYUkPGvcgV2Ho4+9VDWqiu9kTRfk6kdXGDk
cnAnzwIzdzjz+U4vm6s/d/9GlC/zyUacTBVELzPvA1f2phC02MU=
=tr3q
iHUEABYKAB0WIQTNTUNRr6aTP1dKmvuQsrS9eu0jXwUCW3Xq4gAKCRCQsrS9eu0j
Xx/yAQDos+2dUuRWob3Pinw4ekDmBKbqrsGWSB061yhDFV9DcwD+Jn88tyVCqtDf
pRVVjdyOMTuvmKVMXauoRIM4nbN9WQE=
=5W3c
-----END PGP SIGNATURE-----
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