Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
tails
tails
Commits
c230037f
Commit
c230037f
authored
Oct 20, 2020
by
intrigeri
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Release process: make commands easier to copy'n'paste
parent
95811271
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
4 deletions
+13
-4
wiki/src/contribute/release_process.mdwn
wiki/src/contribute/release_process.mdwn
+13
-4
No files found.
wiki/src/contribute/release_process.mdwn
View file @
c230037f
...
...
@@ -1727,10 +1727,19 @@ If you just released a final release
`ssh rsync.lizard sudo rm -rf /srv/rsync/tails/tails/stable/tails-amd64-${PREVIOUS_STABLE_VERSION:?}/`
- our Bittorrent seed: get the previous release's _Transmission_ IDs
(ISO and USB image, use comma-separated values)
with `ssh bittorrent.lizard transmission-remote --list` and then
delete them with
`ssh bittorrent.lizard transmission-remote -t "${PREVIOUS_VERSION_TRANSMISSION_ID:?}" --remove-and-delete`
then re-run `ssh bittorrent.lizard transmission-remote --list` and make sure everything looks good
with:
ssh bittorrent.lizard transmission-remote --list
Then delete them with:
ssh bittorrent.lizard transmission-remote \
-t "${PREVIOUS_VERSION_TRANSMISSION_ID:?}" --remove-and-delete
Finally, check that everything looks good:
ssh bittorrent.lizard transmission-remote --list
1. Remove any remaining RC for the just-published release from
`rsync.lizard:/srv/rsync/tails/tails/alpha/`
1. If you've published a final release, remove IUKs that upgrade to an
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment