Skip to content
Snippets Groups Projects
Commit 34e0f763 authored by Cyril Brulebois's avatar Cyril Brulebois Committed by intrigeri
Browse files

Fix Torrent vs. Torrents: IMG+ISO.

parent 97035069
No related branches found
No related tags found
No related merge requests found
...@@ -1072,7 +1072,7 @@ candidate): ...@@ -1072,7 +1072,7 @@ candidate):
git push origin master git push origin master
) )
## Announce, seed and test the Torrent ## Announce, seed and test the Torrents
Skip this section if [[!tails_ticket 16378]] is not resolved yet. Skip this section if [[!tails_ticket 16378]] is not resolved yet.
...@@ -1093,7 +1093,7 @@ If not, list already running Torrents: ...@@ -1093,7 +1093,7 @@ If not, list already running Torrents:
ssh bittorrent.lizard df -h /var/lib/transmission-daemon/downloads ssh bittorrent.lizard df -h /var/lib/transmission-daemon/downloads
Now you can announce and seed the Torrent for the release you're preparing: Now you can announce and seed the Torrents for the release you're preparing:
cat "${RELEASE_CHECKOUT:?}/wiki/src/tails-signing.key" \ cat "${RELEASE_CHECKOUT:?}/wiki/src/tails-signing.key" \
| ssh bittorrent.lizard gpg --import | ssh bittorrent.lizard gpg --import
...@@ -1151,7 +1151,7 @@ Testing ...@@ -1151,7 +1151,7 @@ Testing
- point them to the up-to-date mirror you've found previously - point them to the up-to-date mirror you've found previously
- make it clear what's the deadline - make it clear what's the deadline
- make it clear where and how you expect to get feedback - make it clear where and how you expect to get feedback
- attach the Torrent - attach the Torrents
- attach the `.packages` file - attach the `.packages` file
1. Make sure someone is committed to run the automated test suite. 1. Make sure someone is committed to run the automated test suite.
1. Make sure that enough people are here to run the tests, that they 1. Make sure that enough people are here to run the tests, that they
...@@ -1164,7 +1164,7 @@ Testing ...@@ -1164,7 +1164,7 @@ Testing
step is and make sure it happens: add to known issues? file ticket? step is and make sure it happens: add to known issues? file ticket?
release blocker? improve the test description (steps, expected outcome)? release blocker? improve the test description (steps, expected outcome)?
1. If [[!tails_ticket 16378]] is not resolved yet, ensure someone will 1. If [[!tails_ticket 16378]] is not resolved yet, ensure someone will
seed the Torrent. seed the Torrents.
Update the website and Git repository Update the website and Git repository
===================================== =====================================
...@@ -1242,7 +1242,7 @@ If preparing a release candidate ...@@ -1242,7 +1242,7 @@ If preparing a release candidate
Skip this part if preparing a final release. Skip this part if preparing a final release.
Copy the signatures and the Torrent into the website repository: Copy the signatures and the Torrents into the website repository:
cp "${ISO_PATH:?}.sig" \ cp "${ISO_PATH:?}.sig" \
"${IMG_PATH:?}.sig" \ "${IMG_PATH:?}.sig" \
... ...
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment