Merge pull request #30 from freedomofpress/release-management-and-sec…

…uredrop-builder

Consolidate and update workstation release management process

docs/conf.py

@@ -316,7 +316,7 @@
     "https://forum.securedrop.org/admin/users/list/active",
     "https://weblate.securedrop.org/projects/securedrop/securedrop/#announcement",
     "https://weblate.securedrop.org/projects/securedrop/securedrop/#repository",
-    "https://github.com/freedomofpress/securedrop-debian-packages-lfs",
+    "https://github.com/freedomofpress/securedrop-apt-prod",
     r"https://weblate.securedrop.org/accounts/profile/.*",
     r"https://github.com/freedomofpress/securedrop/issues/.*",
     r"https://github.com/freedomofpress/securedrop/tree/.*",

docs/release_management.rst

@@ -116,8 +116,8 @@ Pre-Release
 
    c. Build logs should be saved and published according to the `build log guidelines
       <https://github.com/freedomofpress/securedrop/wiki/Build-logs>`_.
-   d. Open a PR on `securedrop-dev-packages-lfs
-      <https://github.com/freedomofpress/securedrop-dev-packages-lfs>`_ that targets the ``main``
+   d. Open a PR on `securedrop-apt-test
+      <https://github.com/freedomofpress/securedrop-apt-test>`_ that targets the ``main``
       branch with the new debs. Do not include tarballs or any debs that would overwrite
       existing debs. Changes merged to this branch will be published to ``apt-test.freedom.press``
       within 15 minutes.
@@ -238,7 +238,7 @@ Release Process
       log guidelines
       <https://github.com/freedomofpress/securedrop/wiki/Build-logs>`_.
 #. In a clone of the private
-   `securedrop-debian-packages-lfs <https://github.com/freedomofpress/securedrop-debian-packages-lfs>`_
+   `securedrop-apt-prod <https://github.com/freedomofpress/securedrop-apt-prod>`_
    repository, create a branch from ``main`` called ``release``.
 #. In your local branch, commit the built packages to the ``core/focal``
    directory.

docs/updating_tor.rst

@@ -12,8 +12,8 @@ Announcements for new Tor releases are posted in the `Tor forum
 <https://forum.torproject.net/c/news/tor-release-announcement/28>`_.
 
 Our continuous integration automatically checks for new Tor packages every
-night and should commit them to the `securedrop-dev-packages-lfs
-<https://github.com/freedomofpress/securedrop-dev-packages-lfs>`_ repository.
+night and should commit them to the `securedrop-apt-test
+<https://github.com/freedomofpress/securedrop-apt-test>`_ repository.
 Within 15 minutes they should be available for download via
 ``apt-test.freedom.press``.
 
@@ -32,5 +32,5 @@ Promoting
 ---------
 
 To promote a Tor release to production, copy the ``*.deb`` files over to the
-`securedrop-debian-packages-lfs <https://github.com/freedomofpress/securedrop-debian-packages-lfs>`_
+`securedrop-apt-prod <https://github.com/freedomofpress/securedrop-apt-prod>`_
 repository and follow those instructions.

docs/workstation_development.rst

@@ -99,7 +99,7 @@ Building workstation deb packages
 
 Debian packages for the SecureDrop Workstation components are maintained
 in a separate repository:
-https://github.com/freedomofpress/securedrop-debian-packaging/
+https://github.com/freedomofpress/securedrop-builder/
 
 Building workstation rpm packages
 ---------------------------------